Bingfeng Mei wrote:
> Sorry, I made a mistake. My local copy of mainline version (still 4.3.0
> 20080213) doesn't gave warning. I just updated my mainline GCC and it
> does give warning now.
I think that you'll find the release 4.3 version does too.
While we try to ensure that gcc warns whenever
: gcc@gcc.gnu.org
Subject: Re: No warning of violating strict aliasing rule and produce
wrong code
Bingfeng Mei wrote:
> Hello,
>
> In following code, gcc (mainline version as well as previous versions)
> produces wrong code without giving any warning regarding strict
aliasing
> violatio
Bingfeng Mei wrote:
> Hello,
>
> In following code, gcc (mainline version as well as previous versions)
> produces wrong code without giving any warning regarding strict aliasing
> violation.
>
> ~/work/trunk-x86/bin/gcc tst.c -O3 -o tst -Wstrict-aliasing=2
> ./tst
> barrier1
> Miscompilation
>
Hello,
In following code, gcc (mainline version as well as previous versions)
produces wrong code without giving any warning regarding strict aliasing
violation.
~/work/trunk-x86/bin/gcc tst.c -O3 -o tst -Wstrict-aliasing=2
./tst
barrier1
Miscompilation
If I compile with
~/work/trunk-x86/bin/
