From: George S. <gsa...@gm...> - 2010-03-26 09:09:27
|
On Fri, Mar 26, 2010 at 4:11 AM, Luca Barbieri <luc...@gm...> wrote: > Are you sure that swrastg and/or any Gallium driver actually load > correctly and work on sparc64? > you are right, I forgot that gallium has its own sync primitives, scratch my reply > This seems to indicate that they use __sync_add_and_fetch_4 assuming > it is a GCC builtin, but GCC does not implement it as a builtin on > sparc64 and neither libgcc nor libc have an implementation of the > function. > > I don't know anything about sparc64, but according to the linux > kernel, I vaguely guess that specifying an high enough -march= to gcc > could solve it by enabling use of atomic instructions that are > otherwise are not used. > > The root cause is likely that we set PIPE_ATOMIC_GCC_INTRINSIC even > though not all __sync builtins are actually supported: we should > probably fix that. > |