This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/42571] internal compiler error: Illegal instruction when handling moon.c file
- From: "badcloud56 at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Jan 2010 19:32:50 -0000
- Subject: [Bug c/42571] internal compiler error: Illegal instruction when handling moon.c file
- References: <bug-42571-18621@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from badcloud56 at yahoo dot com 2010-01-01 19:32 -------
(In reply to comment #2)
> Created an attachment (id=19437)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19437&action=view) [edit]
> fix arm eabi default cpu type
>
> Try this patch, from debian. It corrects arm-eabi to choose an
> armv4t-compatible arm9tdmi as the default cpu type. Otherwise it may generate
> armv5t code, which is consistent with your illegal instruction problem.
>
"Created an attachment (id=19437)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19437&action=view) [edit]
fix arm eabi default cpu type
Try this patch, from debian. It corrects arm-eabi to choose an
armv4t-compatible arm9tdmi as the default cpu type. Otherwise it may generate
armv5t code, which is consistent with your illegal instruction problem."
----
Thanks, but seeing as this is my first time patching what I can assume to be
the gcc binary file, how do I actually *do* it (i.e. which commands)?
> Oh, and please update the "reported against" field: you selected 4.2.2 but
> clearly you used 4.4.2 (4.2.x is no longer supported).
>
Done.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42571