public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/60793] Add target *-*-dragonfly* to dg-options on 172 libstdc++ tests
Date: Wed, 09 Apr 2014 15:52:00 -0000	[thread overview]
Message-ID: <bug-60793-4-2ius9NiRql@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60793-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|testsuite                   |libstdc++

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(Changing component to libstdc++ so it's on my radar)

Could we get some testresults posted to the gcc-testresults list? Preferably
both with and without this change.

I'd prefer not to add it to the target selector if we aren't getting fairly
regular test results, so we can see if the tests are actually passing.


  reply	other threads:[~2014-04-09 15:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 13:04 [Bug testsuite/60793] New: " gnugcc at marino dot st
2014-04-09 15:52 ` redi at gcc dot gnu.org [this message]
2014-04-09 15:59 ` [Bug libstdc++/60793] " gnugcc at marino dot st
2014-04-13 22:44 ` redi at gcc dot gnu.org
2014-04-13 23:01 ` gnugcc at marino dot st
2014-04-14 10:08 ` redi at gcc dot gnu.org
2014-04-14 10:26 ` gnugcc at marino dot st
2014-04-14 11:16 ` manu at gcc dot gnu.org
2014-04-14 11:39 ` gnugcc at marino dot st
2014-04-14 12:08 ` manu at gcc dot gnu.org
2014-04-14 13:55 ` redi at gcc dot gnu.org
2014-04-14 14:07 ` redi at gcc dot gnu.org
2014-05-21 11:48 ` redi at gcc dot gnu.org
2014-05-23 10:20 ` redi at gcc dot gnu.org
2014-05-24 12:08 ` redi 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-60793-4-2ius9NiRql@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).