[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2019-09-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

GitLab Migration User  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|REOPENED|RESOLVED

--- Comment #23 from GitLab Migration User  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/997.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2018-10-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #22 from Ian Romanick  ---
(In reply to freedesktop from comment #21)
> This also popped up on archlinux32 when trying to package mesa for i486:
> 
> /usr/bin/ld: src/intel/vulkan/libanv_common.a(anv_allocator.c.o): in
> function `anv_block_pool_alloc_new':

...

There is no GPU supported by the Intel Vulkan driver that can possibly exist
with a 486 CPU.  Don't build that driver with i486 restrictions.  Same goes for
i915_dri.so and i965_dri.so.  None of those can exist with ARM, Alpha, or MIPS
either.  Use the proper options to configure.ac or Meson to exclude those
drivers on those platforms.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2018-10-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #21 from freedesk...@eckner.net ---
This also popped up on archlinux32 when trying to package mesa for i486:

/usr/bin/ld: src/intel/vulkan/libanv_common.a(anv_allocator.c.o): in function
`anv_block_pool_alloc_new':
anv_allocator.c:(.text+0x1aa): undefined reference to `__sync_fetch_and_add_8'
/usr/bin/ld: anv_allocator.c:(.text+0x307): undefined reference to
`__sync_lock_test_and_set_8'
/usr/bin/ld: src/intel/vulkan/libanv_common.a(anv_allocator.c.o): in function
`anv_free_list_pop':
anv_allocator.c:(.text+0x440): undefined reference to
`__sync_val_compare_and_swap_8'
/usr/bin/ld: src/intel/vulkan/libanv_common.a(anv_allocator.c.o): in function
`anv_free_list_push':
anv_allocator.c:(.text+0x526): undefined reference to
`__sync_val_compare_and_swap_8'
/usr/bin/ld: src/intel/vulkan/libanv_common.a(anv_allocator.c.o): in function
`anv_state_pool_alloc_no_vg':
anv_allocator.c:(.text+0x755): undefined reference to `__sync_fetch_and_add_8'
/usr/bin/ld: anv_allocator.c:(.text+0x7a3): undefined reference to
`__sync_lock_test_and_set_8'


I seem unable to find a source file (only the mentioned *.a and *.o) which
actually tries to use these atomics - any idea, where I should look / try to
patch?

> gcc --version
gcc (GCC) 8.2.1 20180831
> uname -a
Linux arch32-i486-bs0 4.17.6-1-ARCH #1 SMP PREEMPT Wed Jul 18 08:34:04 UTC 2018
i486 GNU/Linux

Best Regards,
Erich

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

Matt Turner  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |---

--- Comment #20 from Matt Turner  ---
(In reply to Jonathan Gray from comment #18)
> (In reply to Matt Turner from comment #16)
> > (In reply to Jonathan Gray from comment #15)
> > > Shocking as it may seem Mesa runs on more than just Linux.
> > 
> > Don't act like that. Grazvydas wrote code to fix a bug you reported more
> > than two years ago. You should be thankful, not sarcastic.
> > 
> > Presumably if you don't piss him off he'd be amenable to fixing other things
> > in this area.
> 
> The problem was clearly stated in the original report.  The changes that
> went in have not addressed this.  Only a variant that concerns a subset. 
> Closing the bug because it fixed the case he cared about and not the actual
> reported problem isn't helping anyone.
> 
> I've had to workaround the breakage for years to be able to ship builds of
> Mesa on multiple architectures.

I think you're inappropriately attributing malice to comments 12 and 14.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

Jonathan Gray  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WONTFIX

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #19 from Timothy Arceri  ---
(In reply to Jonathan Gray from comment #18)
> (In reply to Matt Turner from comment #16)
> > (In reply to Jonathan Gray from comment #15)
> > > Shocking as it may seem Mesa runs on more than just Linux.
> > 
> > Don't act like that. Grazvydas wrote code to fix a bug you reported more
> > than two years ago. You should be thankful, not sarcastic.
> > 
> > Presumably if you don't piss him off he'd be amenable to fixing other things
> > in this area.
> 
> The problem was clearly stated in the original report.  The changes that
> went in have not addressed this.  Only a variant that concerns a subset. 
> Closing the bug because it fixed the case he cared about and not the actual
> reported problem isn't helping anyone.

I don't think he cared about it, he was trying to fix the bug for you.

> 
> I've had to workaround the breakage for years to be able to ship builds of
> Mesa on multiple architectures.

Shocking as it may seem Mesa development in mainly done on Linux for Linux on
non-niche modern hardware. Occasionally things are going to break on systems
untested during development, complaining about an inevitability is not very
helpful.

This is a community project with limited resources, we will always need
contributions from people interested in keeping such platforms building/running
optimally.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #18 from Jonathan Gray  ---
(In reply to Matt Turner from comment #16)
> (In reply to Jonathan Gray from comment #15)
> > Shocking as it may seem Mesa runs on more than just Linux.
> 
> Don't act like that. Grazvydas wrote code to fix a bug you reported more
> than two years ago. You should be thankful, not sarcastic.
> 
> Presumably if you don't piss him off he'd be amenable to fixing other things
> in this area.

The problem was clearly stated in the original report.  The changes that went
in have not addressed this.  Only a variant that concerns a subset.  Closing
the bug because it fixed the case he cared about and not the actual reported
problem isn't helping anyone.

I've had to workaround the breakage for years to be able to ship builds of Mesa
on multiple architectures.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #17 from Matt Turner  ---
(In reply to Grazvydas Ignotas from comment #14)
> Yes but any affected platforms we actually care about?
> 
> Newer gcc should cover some of the cases mentioned in this bug. I think
> pre-v6 ARM now has 32bit atomics on Linux thanks to a kernel helper.
> Others you mentioned are hppa and superh, is anyone actually building mesa
> for those?
> 
> Otherwise it will just be wasted effort for some dead code that nobody ever
> uses.

Gentoo supports both hppa and sh. I find it doubtful that anyone would use Mesa
on sh, but hppa is well maintained. I should have a system running in a few
days on which I can test.

You figured out the solution -- I'm happy to copy-and-paste your small amount
of code to support hppa.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #16 from Matt Turner  ---
(In reply to Jonathan Gray from comment #15)
> Shocking as it may seem Mesa runs on more than just Linux.

Don't act like that. Grazvydas wrote code to fix a bug you reported more than
two years ago. You should be thankful, not sarcastic.

Presumably if you don't piss him off he'd be amenable to fixing other things in
this area.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #15 from Jonathan Gray  ---
Shocking as it may seem Mesa runs on more than just Linux.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #14 from Grazvydas Ignotas  ---
Yes but any affected platforms we actually care about?

Newer gcc should cover some of the cases mentioned in this bug. I think pre-v6
ARM now has 32bit atomics on Linux thanks to a kernel helper.
Others you mentioned are hppa and superh, is anyone actually building mesa for
those?

Otherwise it will just be wasted effort for some dead code that nobody ever
uses.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

Jonathan Gray  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #13 from Jonathan Gray  ---
This is still not handled for 32 bit atomics.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-04-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

Grazvydas Ignotas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #12 from Grazvydas Ignotas  ---
Fixes (partial at least) pushed as a6a38a038bd62e6d9558905f00bef81b5e7e6fcc and
b384c23b9e804916f125354e06c735bd3bb22811. Please reopen if there is still a
problem and specify the environment (architecture, compiler version, any extra
flags).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2017-01-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #11 from Jonathan Gray  ---
Previously 64 bit atomics were contained to i965.  The on disk shader cache
introduced in Mesa 13.0 in 87ab26b2ab35a29d446ae66f1795d40c184c0739 now
requires 64 bit atomics as well which breaks Mesa on 32 bit powerpc which
doesn't have 64 bit atomic instructions:

glxinfo:/usr/X11R6/lib/modules/dri/r300_dri.so: undefined symbol
'__sync_add_and_fetch_8'
libGL error: unable to load driver: r300_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r300
glxinfo:/usr/X11R6/lib/modules/dri/swrast_dri.so: undefined symbol
'__sync_add_and_fetch_8'
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  47
  Current serial number in output stream:  0
name of display: :0

This was reported by Stefan Sperling on OpenBSD/macppc along with the
workaround of using --disable-shader-cache.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2016-09-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

Elmar Hanlhofer  changed:

   What|Removed |Added

 CC||bugzi...@plop.at

--- Comment #10 from Elmar Hanlhofer  ---
Created attachment 126862
  --> https://bugs.freedesktop.org/attachment.cgi?id=126862=edit
i486 __sync_val_compare_and_swap_8 disable debug message

I came across the same problem when I compiled Mesa for the new Plop Linux i486
release. As the affected code is only in a debug message routine in
"intel_debug.c", I simply disabled it. Now it compiles fine with "march=i486".
I attached the patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2016-08-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

Lauri Kasanen  changed:

   What|Removed |Added

 OS|OpenBSD |All
   Hardware|Other   |All

--- Comment #9 from Lauri Kasanen  ---
We're hitting this on TinyCore, and I see Alpine hit it a while back too [1].

We build with -march=i486, and some of the atomics require a 586. Things build,
but some drivers fail to load:

libGL: dlopen /usr/local/lib/dri/i915_dri.so failed
(/usr/local/lib/dri/i915_dri.so: undefined symbol:
__sync_val_compare_and_swap_8)
libGL error: unable to load driver: i915_dri.so
libGL error: driver pointer missing

They should fail to build at the very least. Changing the hw and os to all.

[1] https://bugs.alpinelinux.org/issues/4254

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-12-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #8 from Jonathan Gray  ---
There is no way to backport builtins for architectures that lack atomics at the
ISA level.

On arm/hppa/sh linux has a syscall which the gcc documentation claims can only
do 64 bit values on arm:
https://gcc.gnu.org/wiki/Atomic

Even on Linux with the latest toolchains this should be checked as there are
cases where some or none of the atomics may be present.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-12-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #7 from Emil Velikov  ---
What Matt is saying is that surely Mesa is not the only project out there which
relies on atomics, thus adding (backporting) those in GCC wouldn't be that bad
of an idea.

That aside I'm thinking that porting the libdrm solution wouldn't be that bad
of an idea.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-12-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #5 from Matt Turner  ---
I think if OpenBSD insists on compiling current software with an 8 year old
compiler, they should expect to implement some widely available features in
their fork...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-12-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #6 from Jonathan Gray  ---
I added support for the gnu binary integer constant extension to gcc
specifically for the intel driver in Mesa.  We've also changed the behaviour of
the sync builtins with PIC on i386 to not clobber ebx as well and people are
working on implementing the sync builtins for mips64.  Mesa won't build with
newer versions of out of tree compilers anyway due to the problem misdetecting
SSE4.1 there is another PR for
(https://bugs.freedesktop.org/show_bug.cgi?id=91806).

Even with the latest GCC these atomic builtins won't be available on all
platforms anyway.  Mesa is rapidly becoming i386/amd64/powerpc/sparc64 only.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-12-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #3 from Jose Fonseca  ---
Does OpenBSD supply stdatomic.h?

I wonder if we should start using it on all platforms that supply it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-12-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #4 from Jonathan Gray  ---
No.  And it seems gcc only started supporting C11 atomics in 4.9.

libdrm currently checks for gcc __sync builtins, libatomic-ops and Solaris
atomic.h

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-11-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

Ian Romanick  changed:

   What|Removed |Added

 CC||matts...@gmail.com

--- Comment #1 from Ian Romanick  ---
Matt: I know you're an Alpha fan.  Suggestions?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 93089] mesa fails to check for gcc atomic primitives before using them

2015-11-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93089

--- Comment #2 from Jonathan Gray  ---
It seems mips64 got the sync builtins later than other platforms, they are
available in later versions of gcc but not gcc 4.2.

Alpha also hit an ICE so for now we stopped building Mesa on alpha/mips64 in
OpenBSD.

lib/mesa/src/mesa/main/format_pack.c  -fPIC -DPIC -o main/.libs/format_pack.o   
/usr/xenocara/lib/mesa/src/mesa/main/format_pack.c: In function
'pack_float_bgr_srgb8':  
/usr/xenocara/lib/mesa/src/mesa/main/format_pack.c:6890: error: unrecognizable
insn: 
(insn 259 11 13 2 (set (reg:SF 1 $1)
(const_double:SF 1.220703125e-4 [0x0.8p-12])) -1 (nil)  
(nil))  
/usr/xenocara/lib/mesa/src/mesa/main/format_pack.c:6890: internal compiler
error: in extract_insn, at recog.c:2077

For other architectures we currently build with:

#elif defined(__ARM_ARCH_4__) || defined(__ARM_ARCH_5__) || \
  defined(__hppa__) || defined(__sparc__) || defined(__sh__)
#define PIPE_ATOMIC_UNLOCKED

...

#if defined(PIPE_ATOMIC_UNLOCKED)

#define PIPE_ATOMIC "Unlocked"

#define p_atomic_set(_v, _i) (*(_v) = (_i))
#define p_atomic_read(_v) (*(_v))
#define p_atomic_dec_zero(_v) ((*(_v) -= 1) == 0)
#define p_atomic_inc(_v) (*(_v) += 1)
#define p_atomic_dec(_v) (*(_v) -= 1)
#define p_atomic_add(_v, _i) (*(_v) += (_i))
#define p_atomic_inc_return(_v) (*(_v) += 1)
#define p_atomic_dec_return(_v) (*(_v) -= 1)
#define p_atomic_cmpxchg(_v, old, _new) ({\
__typeof(*_v) _r = *(_v);\
if (*(_v) == old)\
*(_v) = (_new);\
_r;\
})
#endif

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev