Processed: Re: Bug#491653: gcc-4.3: misoptimization of 64-bit bitfield when not byte aligned

Processing commands for [EMAIL PROTECTED]: close 491653 Bug#491653: gcc-4.3: misoptimization of 64-bit bitfield when not byte aligned 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Nick Lewycky [EMAIL PROTECTED] thanks

Bug#491653: gcc-4.3: misoptimization of 64-bit bitfield when not byte aligned

close 491653 thanks Hi Bastian, You're right again, this is entirely due to the effects of strict aliasing rules. The problem goes away with -fno-strict-aliasing. Nick Bastian Blank wrote: On Sun, Jul 20, 2008 at 11:14:10PM -0700, Nick Lewycky wrote: This testcase produces different

Bug#491653: gcc-4.3: misoptimization of 64-bit bitfield when not byte aligned

Package: gcc-4.3 Version: 4.3.1-6 Severity: normal This testcase produces different output depending on whether -O1 or -O2 is specified. Correct: # gcc PR1386.c -o pr1386 -O1 PR1386.c: In function $B!F(Bmain$B!G(B: PR1386.c:15: warning: large integer implicitly truncated to unsigned

Bug#491653: gcc-4.3: misoptimization of 64-bit bitfield when not byte aligned

On Sun, Jul 20, 2008 at 11:14:10PM -0700, Nick Lewycky wrote: This testcase produces different output depending on whether -O1 or -O2 is specified. The testcase is wrong. Please produce a _minimal_ variant, it even shows the same behaviour without bitfields. Please explain what exactly the