This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Proper way to make a one-off multi-file testcase?
- From: Paul Koning <pkoning at equallogic dot com>
- To: hp at bitrange dot com
- Cc: iant at google dot com, joernr at arc dot com, jakub at redhat dot com, gcc at gcc dot gnu dot org
- Date: Fri, 1 Feb 2008 10:21:00 -0500
- Subject: Re: Proper way to make a one-off multi-file testcase?
- References: <20080130211814.GB8600@elsdt-razorfish.arc.com> <20080130215125.GD24264@sunsite.mff.cuni.cz> <20080130223029.GC8600@elsdt-razorfish.arc.com> <m3sl0ej18f.fsf@localhost.localdomain> <20080201074157.B47562@dair.pair.com>
>>>>> "Hans-Peter" == Hans-Peter Nilsson <hp@bitrange.com> writes:
Hans-Peter> On Wed, 30 Jan 2008, Ian Lance Taylor wrote:
>> One issue here is that in some cases const and pure calls can get
>> combined and eliminated even with attribute noinline (unless this
>> changed recently). So in addition to attribute noinline, putting
>> an asm volatile ("") in the function can help make it non-pure and
>> non-const.
Hans-Peter> (The "volatile" is redundant; an asm without in/out
Hans-Peter> operands is always volatile.)
That's what the docs say, but I've seen indications that this is not
actually how it works. (At least not a couple of releases ago.)
paul