public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: resonance@bigfoot.com.au
To: gcc-gnats@gcc.gnu.org
Subject: c/4273: Internal compiler error when compiling a kernel
Date: Sun, 09 Sep 2001 02:16:00 -0000 [thread overview]
Message-ID: <20010909091251.8358.qmail@sourceware.cygnus.com> (raw)
>Number: 4273
>Category: c
>Synopsis: Internal compiler error when compiling a kernel
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Sep 09 02:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Corey Spruit
>Release: gcc-3.0.1, i686-pc-linux-gnu
>Organization:
>Environment:
Slackware linux 8.0, gcc 3.0.1, i686, Duron 950, 450meg ram, arch = k6
>Description:
I was compiling a kernel today, using gcc-3.0.1 (as I just installed it), and it worked fine until:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o acct.o acct.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o capability.o cap
bility.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o ptrace.o ptrace.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o timer.o timer.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o user.o user.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -DEXPORT_SYMTAB -c signal.c
signal.c: In function `kill_proc':
signal.c:716: Unrecognizable insn:
(insn 124 116 117 (parallel[
(set (reg/f:SI 3 ebx [47])
(const_int 0 [0x0]))
(clobber (reg:CC 17 flags))
] ) -1 (insn_list:REG_DEP_ANTI 116 (nil))
(expr_list:REG_UNUSED (reg:CC 17 flags)
(nil)))
signal.c:716: Internal compiler error in insn_default_length, at insn-attrtab.c:223
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
make[2]: *** [signal.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.6/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.6/kernel'
make: *** [_dir_kernel] Error 2
bash-2.05#
You may like to refer to the kernel source for the c file, as it's just kernel 2.4.6 as can be seen. I hope I've included enough info. Thanks. I also have some more info too as follows, and note that gcc 2.95 works fine.
bash-2.05# gcc -dumpversion
3.0.1
bash-2.05# gcc -dumpmachine
i686-pc-linux-gnu
bash-2.05# gcc-2.95.3 -dumpversion
2.95.3
bash-2.05# gcc-2.95.3 -dumpmachine
i386-slackware-linux
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-09-09 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 2:16 resonance [this message]
2001-09-09 2:46 Neil Booth
2001-09-09 3:26 Corey Spruit
2001-09-09 3:26 Neil Booth
2001-09-09 4:51 neil
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=20010909091251.8358.qmail@sourceware.cygnus.com \
--to=resonance@bigfoot.com.au \
--cc=gcc-gnats@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).