From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-410548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 10686 invoked by alias); 21 Dec 2012 18:58:29 -0000
Received: (qmail 10623 invoked by uid 48); 21 Dec 2012 18:58:13 -0000
From: "janis at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/55780] New: effective targets arm_arch_v*_multilib are not strict enough
Date: Fri, 21 Dec 2012 18:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janis at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55780-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: 2012-12/txt/msg02156.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55780

             Bug #: 55780
           Summary: effective targets arm_arch_v*_multilib are not strict
                    enough
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: janis@gcc.gnu.org
                CC: rearnsha@arm.com
            Target: arm


The arm_arch_v*_multilib effective targets check that a minimal C program will
execute when compiled for a particular ARM processor, but the test used is an
empty program and the tests that use those checks have more complicated code. 
All of the effective target checks pass using the gdb arm simulator or QEMU,
but some of the ftest-*.c tests then get illegal instructions or hang.

Checks for the ability to run programs on particular hardware should include
code that will only run on that hardware, as is done for effective target whose
keywords end in "_hw_available".