[OE-core] [PATCH 2/2] libatomics-ops: force omit frame pointer for x86 builds

[Henning Heinold]

On Wed, Jul 17, 2013 at 12:08:51PM +0100, Paul Barker wrote:
> On 17 July 2013 11:45, Phil Blundell <pb at pbcl.net> wrote:
> > On Wed, 2013-07-17 at 16:40 +0800, Jesse Zhang wrote:
> >> Fix failures when building with -fno-omit-frame-pointer (and without
> >> optimization, i.e. -O0):
> >>
> >>     In file included from atomic_ops.h:212:0,
> >>                      from atomic_ops_stack.h:32,
> >>                      from atomic_ops_stack.c:23:
> >>     atomic_ops/sysdeps/gcc/x86.h: In function 'AO_compare_double_and_swap_double_full':
> >>     atomic_ops/sysdeps/gcc/x86.h:148:3: error: 'asm' operand has impossible constraints
> >>        __asm__ __volatile__("xchg %%ebx,%6;" /* swap GOT ptr and new_val1 */
> >
> > This seems like it must be a bug in either GCC or the libatomic-ops
> > source code, and whichever one has the bug ought to be fixed.  Forcing
> > -fomit-frame-pointer might be ok as a temporary measure but it doesn't
> > seem like a very good long-term solution.
> >
> 
> If this is on x86, standard Linux desktop/server distros may have ran
> into the same problem. Maybe worth having a look if/how they handle
> this.

This makes we wonder which software on x86 relies on libatomic-ops anymore?
gcc buildins should be good enough now.

Bye Henning