public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/4273: Internal compiler error when compiling a kernel
@ 2001-09-09 4:51 neil
0 siblings, 0 replies; 5+ messages in thread
From: neil @ 2001-09-09 4:51 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, resonance
Synopsis: Internal compiler error when compiling a kernel
State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Sun Sep 9 04:51:04 2001
State-Changed-Why:
Preprocessed source not provided.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4273&database=gcc
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c/4273: Internal compiler error when compiling a kernel
@ 2001-09-09 3:26 Neil Booth
0 siblings, 0 replies; 5+ messages in thread
From: Neil Booth @ 2001-09-09 3:26 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c/4273; it has been noted by GNATS.
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Corey Spruit <resonance@bigfoot.com.au>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/4273: Internal compiler error when compiling a kernel
Date: Sun, 9 Sep 2001 11:21:44 +0100
We need the preprocessed source. Why don't you read the referenced
URL? Both I and the compiler have asked you to!
You can get the preprocessed source with the -save-temps flag.
Neil.
Corey Spruit wrote:-
> what file do you need? I still have the source of the kernel, and haven't
> touched it, so tell me what file it is, and I could send it.
>
> Corey
>
> On Sun, 9 Sep 2001, Neil Booth wrote:
>
> > resonance@bigfoot.com.au wrote:-
> >
> > > Please submit a full bug report,
> > > with preprocessed source if appropriate.
> > > See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
> >
> > > 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.
> >
> > No, please read the instructions in the URL; we want preprocessed source.
> > If we had to download and configure a kernel for every bug reported,
> > we'd never get time to do anything else.
> >
> > Neil.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c/4273: Internal compiler error when compiling a kernel
@ 2001-09-09 3:26 Corey Spruit
0 siblings, 0 replies; 5+ messages in thread
From: Corey Spruit @ 2001-09-09 3:26 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c/4273; it has been noted by GNATS.
From: Corey Spruit <resonance@bigfoot.com.au>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: c/4273: Internal compiler error when compiling a kernel
Date: Sun, 9 Sep 2001 20:19:02 +1000 (EST)
what file do you need? I still have the source of the kernel, and haven't
touched it, so tell me what file it is, and I could send it.
Corey
On Sun, 9 Sep 2001, Neil Booth wrote:
> resonance@bigfoot.com.au wrote:-
>
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
>
> > 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.
>
> No, please read the instructions in the URL; we want preprocessed source.
> If we had to download and configure a kernel for every bug reported,
> we'd never get time to do anything else.
>
> Neil.
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c/4273: Internal compiler error when compiling a kernel
@ 2001-09-09 2:46 Neil Booth
0 siblings, 0 replies; 5+ messages in thread
From: Neil Booth @ 2001-09-09 2:46 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c/4273; it has been noted by GNATS.
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: resonance@bigfoot.com.au
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/4273: Internal compiler error when compiling a kernel
Date: Sun, 9 Sep 2001 10:41:44 +0100
resonance@bigfoot.com.au wrote:-
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
> 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.
No, please read the instructions in the URL; we want preprocessed source.
If we had to download and configure a kernel for every bug reported,
we'd never get time to do anything else.
Neil.
^ permalink raw reply [flat|nested] 5+ messages in thread
* c/4273: Internal compiler error when compiling a kernel
@ 2001-09-09 2:16 resonance
0 siblings, 0 replies; 5+ messages in thread
From: resonance @ 2001-09-09 2:16 UTC (permalink / raw)
To: gcc-gnats
>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:
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-09-09 4:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-09-09 4:51 c/4273: Internal compiler error when compiling a kernel neil
-- strict thread matches above, loose matches on Subject: below --
2001-09-09 3:26 Neil Booth
2001-09-09 3:26 Corey Spruit
2001-09-09 2:46 Neil Booth
2001-09-09 2:16 resonance
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).