Skip to contentSkip to conversation

PROBLEM: Compiler error for 2.6.0 in fs/proc/array.c

DISCUSSION Kevin Douglas 2 participants 2 messages Dec 19, 2003

lore
Share & tools
lore
#0 lore raw

Compiler error for 2.6.0 in fs/proc/array.c with gcc-2.95 and binutils 2.13.

I received the following error while trying to compile the new 2.6.0 (no -test anything) on my RH 7.3 box. I have gcc version 2.95.3 installed in addion to the yuckie 2.96 from RH. While search the mailing list archives, I found some patches for the -test7 and/or -test8 series that claim they fix a gcc 2.96 bug. I applied the patch on the original 2.6.0 source tree and the compile went through. The patch I'm talking about involved making the tty_nr variable into a volatile int in the file fs/proc/array.c line number 298. There are other patches that attempt to break up the huge sprintf() statement on line 347 into smaller chucks. I'm not sure which would be preferable to the maintainer.

The point of this email is to hopefully bring to your attention a compilation bug in the 2.6.0 source. If I made a mistake and don't have my environment set up correctly, please accept my appologies.

Hope this helps,

-kevin

The actual compiler error:

CC fs/proc/generic.o
CC fs/proc/array.o
fs/proc/array.c: In function `proc_pid_stat':
fs/proc/array.c:398: Unrecognizable insn:
(insn/i 1332 1663 1657 (parallel[

            (set (reg:SI 0 eax)
                (asm_operands ("") ("=a") 0[ 
                        (reg:DI 1 edx)
                    ] 
                    [ 
                        (asm_input:DI ("A"))
                    ]  ("include/linux/times.h") 38))
            (set (reg:SI 1 edx)
                (asm_operands ("") ("=d") 1[ 
                        (reg:DI 1 edx)
                    ] 
                    [ 
                        (asm_input:DI ("A"))
                    ]  ("include/linux/times.h") 38))
            (clobber (reg:QI 19 dirflag))
            (clobber (reg:QI 18 fpsr))
            (clobber (reg:QI 17 flags))
        ] ) -1 (insn_list 1326 (nil))
    (nil))

fs/proc/array.c:398: confused by earlier errors, bailing out make[2]: *** [fs/proc/array.o] Error 1
make[1]: *** [fs/proc] Error 2
make: *** [fs] Error 2

Linux cobra 2.4.22 #1 Fri Nov 7 09:35:24 EST 2003 i686 unknown

Gnu C                  2.96
Gnu make               3.79.1
util-linux             2.11f
mount                  2.11g
module-init-tools      0.9.14
e2fsprogs              1.26
reiserfsprogs          3.x.0j
pcmcia-cs              3.1.22
quota-tools            3.01.
PPP                    2.4.1
isdn4k-utils           3.1pre1
nfs-utils              0.3.1
Linux C Library        2.2.4
Dynamic linker (ldd)   2.2.4
Procps                 3.1.13
Net-tools              1.60
Console-tools          0.3.3
Sh-utils               2.0.11
Modules Loaded         nfs lockd sunrpc eepro100 mii tulip crc32 floppy

raid0 md rtc

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

#1 lore raw
Quoted 10 lines · Kevin Douglas

Compiler error for 2.6.0 in fs/proc/array.c with gcc-2.95 and binutils 2.13.
I received the following error while trying to compile the new 2.6.0 (no -test anything) on my RH 7.3 box. I have gcc version 2.95.3 installed in addion to the yuckie 2.96 from RH. While search the mailing list archives, I found some patches for the -test7 and/or -test8 series that claim they fix a gcc 2.96 bug. I applied the patch on the original 2.6.0 source tree and the compile went through. The patch I'm talking about involved making the tty_nr variable into a volatile int in the file fs/proc/array.c line number 298. There are

Quoted 8 lines

other patches that attempt to break up the huge sprintf() statement on line 347 into smaller chucks. I'm not sure which would be preferable to the maintainer.
The point of this email is to hopefully bring to your attention a compilation bug in the 2.6.0 source. If I made a mistake and don't have my environment set up correctly, please accept my appologies. Hope this helps,
-kevin

What you have found is actually a gcc bug. Upgrade gcc!

-- wli