gcc error?

gcc error?

[billy rose]

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

is the 40+ parameter sprintf() in proc_pid_stat() flushing out a bug in 
gcc on this? ive tried setting the cpu type to 386, 486, and 586 but 
still get the same error.

gcc -v shows 2.96.20000731
redhat 7.3
running kernel 2.4.18-3 or 2.4.20
kernel being compiled is 2.6.4

=====
Billy


[-- Attachment #2: output.txt --]
[-- Type: text/plain, Size: 971 bytes --]

fs/proc/array.c: In function `proc_pid_stat':
fs/proc/array.c:398: Unrecognizable insn:
(insn/i 1334 1666 1660 (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 1328 (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

Re: gcc error?

[Stefan Smietanowski]

billy rose wrote:

> is the 40+ parameter sprintf() in proc_pid_stat() flushing out a bug in 
> gcc on this? ive tried setting the cpu type to 386, 486, and 586 but 
> still get the same error.
> 
> gcc -v shows 2.96.20000731
> redhat 7.3
> running kernel 2.4.18-3 or 2.4.20
> kernel being compiled is 2.6.4

Stop right here.

Update to the latest 2.96 compiler or go to 3.x before proceeding.

I believe that one you have there has more bugs than a windows system.

Well.. Almost. The newer ones were good however but the early ones
weren't.

I'd recommend you install 3.2.x and try again but if you don't then
grab latest errata update to 2.96 and use that. Then if it still
doesn't work you can always ask here again.

// Stefan