public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: yrabinov+business@cs.uchicago.edu
To: gcc-gnats@gcc.gnu.org
Subject: c/9933: "internal error: Illegal instruction" when compiling 2.4.20 linux kernel
Date: Tue, 04 Mar 2003 04:56:00 -0000 [thread overview]
Message-ID: <20030304045329.25022.qmail@sources.redhat.com> (raw)
>Number: 9933
>Category: c
>Synopsis: "internal error: Illegal instruction" when compiling 2.4.20 linux kernel
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 04 04:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Eugene Rabinovich
>Release: gcc version 3.2.2
>Organization:
>Environment:
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/specs
Configured with: ../gcc-3.2.2/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i386-slackware-linux --host=i386-slackware-linux
Thread model: posix
I am running Linux (Slackware 9.0beta)
>Description:
When I tried to compile with -save-temps, the same file compiled fine.
I am attaching vfs.i. I then deleted vfs.i and vfs.o
>How-To-Repeat:
Configure the linux kernel, make dep, make bzlilo.
Compile dies on file "vfs.c" in function `nfsd_link'
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="vfs.i"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="vfs.i"
next reply other threads:[~2003-03-04 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 4:56 yrabinov+business [this message]
2003-03-04 10:10 ebotcazou
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=20030304045329.25022.qmail@sources.redhat.com \
--to=yrabinov+business@cs.uchicago.edu \
--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).