public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51251] SPARC _64 instructions in V7 executables
Date: Mon, 21 Nov 2011 12:44:00 -0000	[thread overview]
Message-ID: <bug-51251-4-WPflDMM0mv@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

--- Comment #6 from Joel Sherrill <joel at gcc dot gnu.org> 2011-11-21 12:21:26 UTC ---
(In reply to comment #5)
> > Hmmm... because of the way the test is compiled and the target flags are added,
> > there is ... "-mcpu=ultrasparc -mvis" and then later on the command line
> > "-mcpu=cypress".  I wonder what that results in other than a mess.
> 
> Whoever automatically adds -mcpu=cypress without checking whether there isn't
> already a -mcpu switch specified by the user is the culprit.

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.

We have seen this before on arm and powerpc targets. In those cases, the tests
or scripts had something added to them. Janice Johnson tinkered with the
testsuite to address a similar failure on PowerPC. I found this message in the
thread.

 http://lists.gnu.org/archive/html/dejagnu/2008-12/msg00012.html

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.


  parent reply	other threads:[~2011-11-21 12:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  1:52 [Bug target/51251] New: " 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 [this message]
2011-11-21 13:31 ` [Bug testsuite/51251] conflicting -mcpu switches during testing ebotcazou at gcc dot gnu.org
2011-11-21 14:59 ` 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-WPflDMM0mv@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: link
Be 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).