From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20444 invoked by alias); 21 Nov 2011 14:07:20 -0000 Received: (qmail 20338 invoked by uid 22791); 21 Nov 2011 14:07:19 -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; Mon, 21 Nov 2011 14:06:32 +0000 From: "joel at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/51251] conflicting -mcpu switches during testing Date: Mon, 21 Nov 2011 14:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joel at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-11/txt/msg02118.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51251 --- Comment #8 from Joel Sherrill 2011-11-21 14:06:27 UTC --- (In reply to comment #7) > > The issue is that when running on real hardware, you can't use arbitrary cpu > > flags and expect it to work. And it is wrong to say xfail on sparc-rtems > > because they could work on another board running rtems. Just not this one. > > ...yes, that's why we have the dg-require-effective-target framework now. I am thinking this may be a broader case than just that the CPU model on the target doesn't have a particular feature. sparc-rtems is different from sparc64-rtems. sparc-rtems is ONLY 32-bit v7 and v8. What's the simplest way to indicate that no 64-bit, VIS, etc tests are applicable?