From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-372394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 2474 invoked by alias); 30 Oct 2011 12:46:05 -0000
Received: (qmail 2465 invoked by uid 22791); 30 Oct 2011 12:46:04 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 30 Oct 2011 12:45:51 +0000
From: "oleg.endo@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50694] SH Target: SH2A little endian does not actually work
Date: Sun, 30 Oct 2011 12:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: oleg.endo@t-online.de
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-50694-4-l3ZaMHWW3b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50694-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-10/txt/msg03138.txt.bz2

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.