From: Andrew Haley <aph@redhat.com>
To: tanle <lmtan91@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Internal Compiler Error
Date: Mon, 24 Dec 2012 18:19:00 -0000 [thread overview]
Message-ID: <50D89C92.4030603@redhat.com> (raw)
In-Reply-To: <50D8865D.806@gmail.com>
Please son't cross-post to gcc and gcc-help.
On 12/24/2012 04:44 PM, tanle wrote:
> Could you explain for you about "Internal Compiler Error"?
> I am building the Linux kernel for microbalze (Atlys Board), there are
> some errors as:
> fs/ext2/super.c: In function 'ext2_fill_super':
> fs/ext2/super.c:1144:1: internal compiler error: in reload, at
> reload1.c:1059
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> make[2]: *** [fs/ext2/super.o] Error 1
> make[1]: *** [fs/ext2] Error 2
> make: *** [fs] Error 2
> I use gcc version 4.6.1
It's a bug in the compiler. If you report it, someone might
fix it.
Andrew.
next prev parent reply other threads:[~2012-12-24 18:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 16:44 tanle
2012-12-24 18:19 ` Andrew Haley [this message]
2012-12-27 17:27 ` Iyer, Balaji V
-- strict thread matches above, loose matches on Subject: below --
2018-01-19 13:17 internal compiler error Matt Sexton via gcc-help
2018-01-19 13:26 ` Mikhail Maltsev
2018-01-19 14:35 ` Matt Sexton via gcc-help
2018-01-19 15:54 ` Matt Sexton via gcc-help
2018-01-22 13:14 ` Mason
2018-01-22 13:21 ` Matt Sexton via gcc-help
2010-07-12 9:04 Malte.Mauelshagen
2010-07-12 9:56 ` Ian Lance Taylor
2008-02-29 21:27 raian.ufop
2008-02-29 22:16 ` Brian Dessent
2008-03-03 18:50 ` raian.ufop
2003-07-30 20:29 Internal " DEEPA SIVASANKARANE
2001-07-03 8:36 Av Vl
2001-07-02 8:04 Av Vl
1999-09-29 12:58 Guardian
1999-09-30 3:33 ` jwk
1999-09-30 23:56 ` jwk
1999-10-01 0:00 ` jwk
1999-10-01 13:49 ` Guardian
1999-10-31 13:57 ` Guardian
1999-09-30 23:56 ` Guardian
1999-10-01 0:00 ` Guardian
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=50D89C92.4030603@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lmtan91@gmail.com \
/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).