Re: toolchain/45673: gcc on i386 current generates bad code for assembler code in lock.h

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

The following reply was made to PR toolchain/45673; it has been noted by GNATS.

From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: toolchain/45673: gcc on i386 current generates bad code for
 assembler code in lock.h
Date: Tue, 13 Mar 2012 22:11:08 -0400

 On Wed, 14 Mar 2012 11:50:50 +1100
 matthew green <mrg%eterna.com.au@localhost> wrote:
 
 > 
 > > From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
 > > To: gnats-bugs%NetBSD.org@localhost
 > > Cc: 
 > > Subject: Re: toolchain/45673: gcc on i386 current generates bad code for
 > >  assembler code in lock.h
 > > Date: Tue, 13 Mar 2012 20:30:02 -0400
 > > 
 > >  On Mon, 12 Mar 2012 05:35:02 +0000 (UTC)
 > >  Matthew Mondor <mm_lists%pulsar-zone.net@localhost> wrote:
 > >  
 > >  >  I am also encountering this problem in a netbsd-6/amd64 build attempt
 > >  >  today.  Also, pkg/45814 seems to be related.
 > >  
 > >  Just for more information, to trigger this bug when building
 > >  netbsd-6/amd64, I have to add DBG=-g to /etc/mk.conf
 > 
 > that sounds like a bad idea.  you're missing -O2 now, which may be
 > why gcc is getting the asm wrong...
 > 
 > i use DBG=-g -O2.
 
 Indeed the build succeded with -O2.  I had assumed that -g without -O2
 would have used -O0 and that it could not be problematic, but even be
 more useful for debugging.
 
 Thanks for the tip,
 -- 
 Matt