public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: chris@imi.com.au
To: gcc-gnats@gcc.gnu.org
Subject: c/4985: GCC 3.0.1 and 3.0.2 report an internal compiler error when compiling the 8139too module in linux kernel 2.4.16
Date: Sun, 02 Dec 2001 23:46:00 -0000	[thread overview]
Message-ID: <20011203074115.23000.qmail@sources.redhat.com> (raw)


>Number:         4985
>Category:       c
>Synopsis:       GCC 3.0.1 and 3.0.2 report an internal compiler error when compiling the 8139too module in linux kernel 2.4.16
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Dec 02 23:46:02 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Chris Nolan
>Release:        3.0.1 and 3.0.2
>Organization:
>Environment:
Linux Mandrake 8.1
>Description:
Using either the precompiled version of GCC 3.0.1 that comes with Mandrake 8.1 or compiling GCC 3.0.2 from the source produces the same error. The error occurs when compiling the 8139too (RTL 8139) module. I have not modified the configure scripts or makefiles included in the distribution of either the kernel or the GCC source. The only switch that I can think of that may have caused this problem is --march=athlon .

This problem occurs whether the module is complied into the kernel or as a module.
>How-To-Repeat:
Enable support for the Realtek 8139 series of LAN boards in the kernel, try to make bzImage and gaze at the result. :-)
>Fix:
I am but a lowly second year software engineering student. I'm not a god like those who maintain GCC. :-)
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-12-03  7:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02 23:46 chris [this message]
2001-12-03  7:47 rodrigc
2001-12-03  7:56 rodrigc

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=20011203074115.23000.qmail@sources.redhat.com \
    --to=chris@imi.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).