All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Paris <jim@jtan.com>
To: linux-mips@oss.sgi.com
Subject: native gcc-3.0.1?
Date: Thu, 20 Sep 2001 01:57:42 -0400	[thread overview]
Message-ID: <20010920015742.A8317@neurosis.mit.edu> (raw)

Does anyone have gcc-3.0.1 built as a native MIPS compiler?
I have a 3.0.1 cross-compiler that seems to work fine, but when I
cross-compiled a native gcc-3.0.1, it doesn't work:

# cat hello.c
main() 
{
    printf("hello, world\n");
}
# gcc -c hello.c
hello.c: In function 'main':
hello.c:4: Internal error: Illegal instruction
Please submit a full bug report
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

It's possible that

1) My kernel is broken.  I doubt this, only because the other
   possibilities seem more likely; I suppose I could add debugging
   output to all of the places where the kernel generates SIGILL
2) My cross-compiler is broken.  But, everything else it's compiled
   has worked fine, including relatively complicated programs like
   strace and bash.

It could also be that gcc-3.0.1 is simply broken when running natively
on MIPS.  Has anyone done this?  Any luck?

It's also possible (and I think likely) that my cross-compiler is
making wrong assumptions about the target system (since ./configure
can be pretty dumb when it comes to setting up a cross compile).  If
anyone has built gcc-3.0 or gcc-3.0.1 natively on MIPS, can you send
me the config.cache from your build?

I tried using my gcc-3.0.1 cross-compiler to build a native gcc-2.95.3
instead, but the newer GCCs doesn't seem to happy about building old
ones.  Grr..

-jim

             reply	other threads:[~2001-09-20  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20  5:57 Jim Paris [this message]
2001-09-20  6:09 ` native gcc-3.0.1? Ryan Murray
2001-09-20 10:00   ` william

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=20010920015742.A8317@neurosis.mit.edu \
    --to=jim@jtan.com \
    --cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.