public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/4273: Internal compiler error when compiling a kernel
Date: Sun, 09 Sep 2001 03:26:00 -0000 [thread overview]
Message-ID: <20010909102602.31697.qmail@sourceware.cygnus.com> (raw)
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.
next reply other threads:[~2001-09-09 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 3:26 Neil Booth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-09 4:51 neil
2001-09-09 3:26 Corey Spruit
2001-09-09 2:46 Neil Booth
2001-09-09 2:16 resonance
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=20010909102602.31697.qmail@sourceware.cygnus.com \
--to=neil@daikokuya.demon.co.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).