public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/55780] effective targets arm_arch_v*_multilib are not strict enough
Date: Tue, 19 Feb 2013 23:53:00 -0000	[thread overview]
Message-ID: <bug-55780-4-d1LHob9qWl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55780-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from Janis Johnson <janis at gcc dot gnu.org> 2013-02-19 23:53:05 UTC ---
The gcc.target/arm/ftest-*.c tests now work without hangs, but the effective
target checks are still in the testsuite available to be used by other tests
where they will show the same problems.  These effective target checks could be
useful, but not in their current state.


      parent reply	other threads:[~2013-02-19 23:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 18:58 [Bug testsuite/55780] New: " janis at gcc dot gnu.org
2013-01-02 12:17 ` [Bug testsuite/55780] " gretay at gcc dot gnu.org
2013-01-03 22:52 ` janis at gcc dot gnu.org
2013-01-15 15:52 ` aldyh at gcc dot gnu.org
2013-02-19 23:41 ` ramana at gcc dot gnu.org
2013-02-19 23:53 ` janis at gcc dot gnu.org [this message]

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-55780-4-d1LHob9qWl@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).