search for: pushable

...ther repo as the primary repository, repo.or.cz in particular. Considering the issues until recently with git.zytor.com and the situation with git.kernel.org along with the fact I already push to multiple repos, I think this may be a good time to look at maintaining multiple official repos that are pushable. As it stands, repo.or.cz has a repo that's a mirror-mode (not pushable) created by Sebastian Herbszt, a past contributor. There's also a namespace on github.com that could be used. hpa/Matt, with your permission I'd like to work on your behalf to get both of these prepared and up to...

...repo.or.cz in particular. Considering the >> issues until recently with git.zytor.com and the situation with >> git.kernel.org along with the fact I already push to multiple repos, I >> think this may be a good time to look at maintaining multiple official >> repos that are pushable. > > What's the situation with git.kernel.org? I currently have access to push to the official repo at git.zytor.com but not git.kernel.org. It's my understanding that getting me access to git.kernel.org would take quite a bit of effort, approvals, and probably exceptions. >>...

...ragma clang section bss(".mybss") rodata(".myrodata") data(".mydata") > text(".mytext") > > The pragma applies to all global variable and function declarations from > the pragma to the end of the translation unit. The pragma should ideally be > pushable and poppable, but that is outside the scope of this RFC. The > pragma also applies to static local declarations within functions. > > All global variables and functions affected by this pragma have their > default ELF section destinations changed. Globals with > __attribute__((sectio...

...mary repository, repo.or.cz in particular. Considering the > issues until recently with git.zytor.com and the situation with > git.kernel.org along with the fact I already push to multiple repos, I > think this may be a good time to look at maintaining multiple official > repos that are pushable. What's the situation with git.kernel.org? > As it stands, repo.or.cz has a repo that's a mirror-mode (not > pushable) created by Sebastian Herbszt, a past contributor. There's > also a namespace on github.com that could be used. Still lurking around. > hpa/Matt, with y...

...g it its own way. Docs are pages 108/109 here: http://www.ece.ualberta.ca/~cmpe490/documents/ghs/build_arm.pdf Jon > > The pragma applies to all global variable and function declarations > from the pragma to the end of the translation unit. The pragma > should ideally be pushable and poppable, but that is outside the > scope of this RFC. The pragma also applies to static local > declarations within functions. > > All global variables and functions affected by this pragma have > their default ELF section destinations changed. Globals with >...

...er prospects in existence. >> >> 8_ For any of the potential prospects, actions should be taken so "The >> Syslinux Project" could acquire official ownership / privileges / >> permissions. At the moment, my thoughts are simple: 1) Add at _least_ one more official pushable repo. I'd consider adding repo.or.cz, github.com and gitlab.com (gitorious.org is being acquired by gitlab.com and being shutdown) as official repos. Adding permissions to any of these should be relatively easy. 2) Change the primary repo from git.kernel.org. Depending on hpa's thoughts...

On Sat, Jun 13, 2015 at 10:44:11PM +0300, Ady via Syslinux wrote: > > > I'm starting this thread to discuss what git repository should be > > designated as primary and which repositories should be designated as > > secondary. > > > > For years, git.kernel.org has been the primary repo, updated at least > > with every full and pre- release.

...kin/mesa/commits/atomic3 which has working ARB_shader_atomic_counters and ARB_shader_storage_buffer_object support (while ripping out things like TGSI_FILE_RESOURCE). Still working on proper memory qualifier support, and obviously need to do some cleanup before upstreaming. Should be getting into a pushable state probably early January. Cheers, -ilia On Wed, Dec 16, 2015 at 12:24 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > I believe that your problem is this: > > /*01a0*/ LD R8, [R8]; > /* 0x8000000000821c85 */ > > That needs to...

...here: > http://www.ece.ualberta.ca/~cmpe490/documents/ghs/build_arm.pdf > > > Jon > > > > > The pragma applies to all global variable and function declarations > > from the pragma to the end of the translation unit. The pragma > > should ideally be pushable and poppable, but that is outside the > > scope of this RFC. The pragma also applies to static local > > declarations within functions. > > > > All global variables and functions affected by this pragma have > > their default ELF section destinations ch...

I believe that your problem is this: /*01a0*/ LD R8, [R8]; /* 0x8000000000821c85 */ That needs to be LD.E (and your ST's need to be ST.E). You're using a 32-bit gmem address, but you need to be using a 64-bit one. I believe the 32-bit ones work on fermi, but afaik not on Kepler. Cheers, -ilia On Wed, Dec 16, 2015 at 12:06 PM, Hans de Goede