This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/50694] SH Target: SH2A little endian does not actually work
- From: "oleg dot endo at t-online dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 30 Oct 2011 12:45:30 +0000
- Subject: [Bug target/50694] SH Target: SH2A little endian does not actually work
- Auto-submitted: auto-generated
- References: <bug-50694-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50694
--- Comment #9 from Oleg Endo <oleg.endo@t-online.de> 2011-10-30 12:45:30 UTC ---
(In reply to comment #8)
> (In reply to comment #7)
>
> This problem doesn't require the theoretical/mathematical
> completeness. There are many inappropriate combinations
> of options which don't get any warning when running compiler
> and configurations. The important thing is to warn very
> confusing ones from the user's point of view. So your patch
> in #6 or even one liner in #2 would be OK and enough for
> this PR, I think.
OK. I think the SH1 check should be left out completely in this case.
If it is included, the default configuration (-m1 -mb) will fail to build
e.g. newlib. I'd propose catching the SH2A case only, considering the user's
default -mb / -ml configuration. If somebody configures the default to be -m2a
-ml then it will fail to build, but I guess only very few people will try to do
that anyway.