public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/51251] conflicting -mcpu switches during testing Date: Mon, 21 Nov 2011 13:31:00 -0000 [thread overview] Message-ID: <bug-51251-4-sAAISw0CLE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51251-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51251 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |testsuite Summary|SPARC _64 instructions in |conflicting -mcpu switches |V7 executables |during testing --- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-11-21 12:43:45 UTC --- > The board in question is really a V7 and that is the proper cpu selection. It > is added by the test framework in a dejagnu board file. OK, but adding it like so is wrong. Suppose that a SPARC-specific test checks that some feature available only in V8 works; by adding -mcpu=cypress without further ado, you'll most likely make the test fail. Overriding compiler switches in tests is a no-no and... > 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.
next prev parent reply other threads:[~2011-11-21 12:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-21 1:52 [Bug target/51251] New: SPARC _64 instructions in V7 executables joel at gcc dot gnu.org 2011-11-21 2:05 ` [Bug target/51251] " joel at gcc dot gnu.org 2011-11-21 7:44 ` davem at davemloft dot net 2011-11-21 7:47 ` davem at davemloft dot net 2011-11-21 8:13 ` burnus at gcc dot gnu.org 2011-11-21 12:23 ` ebotcazou at gcc dot gnu.org 2011-11-21 12:44 ` joel at gcc dot gnu.org 2011-11-21 13:31 ` ebotcazou at gcc dot gnu.org [this message] 2011-11-21 14:59 ` [Bug testsuite/51251] conflicting -mcpu switches during testing joel at gcc dot gnu.org 2011-11-21 19:30 ` davem at gcc dot gnu.org 2011-11-22 0:04 ` joel at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-51251-4-sAAISw0CLE@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).