mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: billy rose <billyrose@cox-internet.com>
To: linux-kernel@vger.kernel.org
Subject: gcc error?
Date: Wed, 17 Mar 2004 13:22:35 -0600	[thread overview]
Message-ID: <4058A57B.4040006@cox-internet.com> (raw)

[-- 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

             reply	other threads:[~2004-03-17 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 19:22 billy rose [this message]
2004-03-17 20:20 ` Stefan Smietanowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4058A57B.4040006@cox-internet.com \
    --to=billyrose@cox-internet.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®