This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/12154] mips/amd/gcc/mvista/glib internal error: Segmentation fault
- From: "drow at mvista dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Sep 2003 15:05:09 -0000
- Subject: [Bug c/12154] mips/amd/gcc/mvista/glib internal error: Segmentation fault
- References: <20030903153736.12154.andreww@bemac.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
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 drow at mvista dot com 2003-09-08 15:05 -------
Subject: Re: mips/amd/gcc/mvista/glib internal error: Segmentation fault
On Mon, Sep 08, 2003 at 08:35:23AM -0000, andreww at bemac dot com wrote:
> 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?
It'll use MIPS I unless you tell it otherwise, unless you've told it
not to.