--- Comment #6 from ramana at gcc dot gnu dot org 2010-01-04 11:26 ---
The default is set to be v5t rather than v4t because interworking is enabled by
default for v5t. In case you want a GNU/ Linux toolchain with v4t , you need
to make sure interworking is enabled and all shared librari
--- Comment #5 from badcloud56 at yahoo dot com 2010-01-01 19:57 ---
(In reply to comment #4)
> (In reply to comment #3)
> > 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 co
--- Comment #4 from mikpe at it dot uu dot se 2010-01-01 19:48 ---
(In reply to comment #3)
> 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 illega
--- 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
--- Comment #2 from mikpe at it dot uu dot se 2010-01-01 17:37 ---
Created an attachment (id=19437)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19437&action=view)
fix arm eabi default cpu type
Try this patch, from debian. It corrects arm-eabi to choose an
armv4t-compatible arm9t
--- Comment #1 from badcloud56 at yahoo dot com 2010-01-01 15:53 ---
Created an attachment (id=19435)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19435&action=view)
*.i filegenerated by adding -save-temps
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42571
