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

["Kai-Uwe Eckhardt" <kuehro%gmx.de@localhost>]

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

From: "Kai-Uwe Eckhardt" <kuehro%gmx.de@localhost>
To: David Laight <david%l8s.co.uk@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: re: toolchain/45673: gcc on i386 current generates bad code for
 assembler code in lock.h
Date: Wed, 14 Mar 2012 11:31:47 +0100

 > That just avoid the bug - it really shouldn't happen.
 > 
 
 Yes, but at least it doesn't silently create bad code without warning.
 This is along standing issue on gcc, but it is only triggered in rare
 cases. Fixing it seems to require considerable changes in gcc, so it
 won't change soon. We just have to be aware that our base compiler has
 problems with this and we know how to fix it by using more conservative
 register hints or compiler flags. 
 
 Kai-Uwe
 
 
 -- 
 --