Bug#151196: gcc-2.95.4-9 ICE in kernel (matroxfb) code

and 'wontfix', but not 'fixed'. Thanks, Petr Vandrovec [EMAIL PROTECTED] -- To UNSUBSCR

Bug#151196: gcc-2.95.4-9 ICE in kernel (matroxfb) code

) and gcc-3.1 (3.1.1-0pre2) compile code flawlessly. Best regards, Petr Vandrovec [EMAIL PROTECTED] $ gcc-2.95 -W -Wall -O2 bug.c bug.c: In function `comput

Bug#107123: Non-optimal code generated by gcc-3.0

ck variables which were optimized, but then somehow left in stack frame. Thanks, Petr Vandrovec [EMAIL PROTECTED] struct blockInt { unsigned int cnt; }; void __freeblock(struct blo

Re: Bug#106716: gcc-3.0.1 refuses to compile Linux kernel

it should threw unused portions of inlined __constant_memcpy out, should not? (and I do not believe that after this throwing out copy_siginfo size is 143...) Thanks, Petr Vandrovec [E

Bug#106716: gcc-3.0.1 refuses to compile Linux kernel

On 26 Jul 01 at 16:11, Ben Collins wrote: > On Thu, Jul 26, 2001 at 08:27:14PM +0200, Petr Vandrovec wrote: > > Package: gcc-3.0 > > Version: 3.0.1-0pre010723 > > to change code to not inline, and I agree with him - 100 is completely > > stupid, backward incompatible li

Bug#106716: gcc-3.0.1 refuses to compile Linux kernel

Thanks, Petr Vandrovec [EMAIL PROTECTED]

Bug#100983: gcc-3.0-010613 refuses to compile programs

Thanks, Petr Vandrovec [EMAIL PROTECTED]

Bug#100535: gcc-3.0-20010610 refuses to compile correct

yword present in it! Alan Cox just told me that he applied my patch to kernel, so gcc maintainer can just close this bug. Or can I do that myself? Best regards, Petr Vandrovec [EMAIL PROTECTED]

Bug#100535: gcc-3.0-20010610 refuses to compile correct (?) code

xtime; volatile struct timeval xtime; --- vana:~$ gcc -c -W -Wall xx.c xx.c:5: conflicting types for `xtime' xx.c:3: previous declaration of `xtime' vana:~$ gcc-2.95 -c -W -Wall xx.c vana:~$ Thanks, Petr