Re: Why not use GCC 3.0?

[Jerome Warnier <jerome.warnier@chello.be>]

mgv@vindul.com wrote:

> On 07.Mar.02-16:28, Jerome Warnier wrote:
>
> > Christopher C. Chimelis wrote:
> >
> > > On Tue, 5 Mar 2002, Jerome Warnier wrote:
> > I know personnaly (physically) at least three Alpha owners (including 
> > myself) under Linux (or willing to).
> not yet a great number, but please add one more;
>
> no way to compile 2.4.17 with 2.95/3.0: a lot of "undefined reference
> to ..." with O0 and all this with O2 (long lines wrapped):
How did you do to compile it with gcc-3.0?
Did you compile it as module?

> make[3]: Entering directory `/usr/src/linux/drivers/block'
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes\
>    -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing \
>    -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6\
>    -c -o DAC960.o DAC960.c
> DAC960.c: In function `DAC960_V2_EnableMemoryMailboxInterface':
> DAC960.c:1053: internal error--unrecognizable insn:
> (insn 1044 1040 481 (set (reg:DI 16 $16)
>        (plus:DI (reg:DI 30 $30)
>            (const_int 4398046511104 [0x40000000000]))) -1 (nil)
>    (nil))
> cpp0: output pipe has been closed
> make[3]: *** [DAC960.o] Error 1
> make[3]: Leaving directory `/usr/src/linux/drivers/block'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux/drivers/block'
> make[1]: *** [_subdir_block] Error 2
> make[1]: Leaving directory `/usr/src/linux/drivers'
> make: *** [_dir_drivers] Error 2
I had exactly the same problem, which I resolved using gcc-3.0 and 
compiling it in the kernel (not as module).

> Obviously, running like a charm with:
>
> Linux x.x.x 2.2.19 #5 Wed Feb 16 20:13:38 CET 2002 alpha unknown
>
> Ciao
> Marco