public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andreww at bemac dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12154] mips/amd/gcc/mvista/glib  internal error: Segmentation fault
Date: Mon, 08 Sep 2003 08:35:00 -0000	[thread overview]
Message-ID: <20030908083523.16840.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030903153736.12154.andreww@bemac.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12154



------- Additional Comments From andreww at bemac dot com  2003-09-08 08:35 -------
Another question about using the onboard mips gcc...

Should the ./configure script have put a -mips2 or a CPU=MIPS32 into
the compiler string?

Or since the compiler was built for the board this is already the 
default built in options?

If so, could there be some problem that this compiler is expecting
a particular kind of mips processor with some features/instructions
which my au1500 doesn't have?

Can I see which mips processor it thinks it is compiling for?

Or is it the case that gcc will just pick the common instructions?

thanks again,

andy


  parent reply	other threads:[~2003-09-08  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 15:37 [Bug c/12154] New: " andreww at bemac dot com
2003-09-03 15:40 ` [Bug c/12154] " andreww at bemac dot com
2003-09-03 19:28 ` rsandifo at gcc dot gnu dot org
2003-09-04 14:00 ` andreww at bemac dot com
2003-09-04 14:07 ` andreww at bemac dot com
2003-09-04 14:35 ` andreww at bemac dot com
2003-09-04 14:42 ` pinskia at gcc dot gnu dot org
2003-09-04 14:59 ` andreww at bemac dot com
2003-09-04 22:51 ` drow at mvista dot com
2003-09-05  8:26 ` andreww at bemac dot com
2003-09-08  8:35 ` andreww at bemac dot com [this message]
2003-09-08 15:05 ` drow at mvista dot com
2004-01-01  3:13 ` pinskia at gcc dot gnu dot org

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=20030908083523.16840.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).