From:	"Nick Kurshev" <nickols_k AT mail DOT ru>
To:	"pgcc AT delorie DOT com" <pgcc AT delorie DOT com>
Date:	Tue, 09 Jan 2001 19:46:37 +0000 (:)
X-Mailer:	PMMail 2.00.1500 for OS/2 Warp 4.05
MIME-Version:	1.0
Subject:	pgcc-2.95.2.1 does not compile a Linux-kernel and has other bugs
Message-Id:	<E14G1vE-0008w4-00@smtp4.port.ru>
Reply-To:	pgcc AT delorie DOT com

Hello!

My hardware: AMD-K6 / 128MB RAM
My operating system: Linux-Mandrake 7.0 (Air)
Currently installed Linux-Lernel: 2.2.18

I have compiled new pgcc-2.95.2.1 with following keys (three times):
-march=k6 -mcpu=k6 -mmmx -fschedule-insns2 -O3 -fomit-frame-pointer -pipe -ffast-math
With those keys I had compiled many other parts of my Mandrake.

I did an attempt to compile linux-2.2.19-pre.6 with new pgcc-2.95.2.1, but compiler was not able
to compile file console.c with following message:

STDOUT:
cc -D__KERNEL__ -I/usr/src/linux-2.2.19-pre.6/include -Wall -Wstrict-prototypes -march=k6 -mcpu=k6 
-mmx-only -fschedule-insns2 -O3 -fomit-frame-pointer -mschedule-prologue -momit-leaf-frame-pointer -mmove 
-fmove-all-movables -freduce-all-givs -fexpensive-optimizations -fregmove -foptimize-register-move 
-fno-exceptions -fno-rtti -pipe -fno-strict-aliasing -pipe -fno-strength-reduce -march=k6 -mcpu=k6 -mmmx-only 
-malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586   -DEXPORT_SYMTAB -c console.c

STDERR:
console.c: In function `take_over_console':
console.c:2453: internal error--insn does not satisfy its constraints:
(insn 501 441 442 (set (reg:HI 17 %mm0)
        (mem:HI (plus:SI (reg:SI 6 %ebp)
                (const_int -12 [0xfffffff4])) 0)) 52 {movhi+1} (nil)
    (nil))
cpp: output pipe has been closed

Also I have compiled BASH with new compiler with same keys as kernel, but anew compiled bash
was not able to handle command line arguments propertly. As effect kernel at boot time could not execute 
any scripts in /etc/init.d, command "make install" does not work e.t.c.

And last observation: New compiler (pgcc-2.95.2.1)  is stopped too frequently ( by signals of different kind:
such as: 4, 9, 11). As rule, gcc received signal #11 or #9 only when memory is exhausted. But in this case 
free memory was ~50Mb. Also it does not remove wrongly generated .o file after receiving such signals. (but 
gcc does it).

Best regards! Nick

- Raw text -