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++/51296] Several 30_threads tests FAIL on Tru64 UNIX
Date: Wed, 11 Jan 2012 16:50:00 -0000	[thread overview]
Message-ID: <bug-51296-4-qSg8WG2RHe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51296-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-01-11 16:50:09 UTC ---
Regarding the remaining failures, it appears to be a front-end issue. Fixing it
in the library could be done with an autoconf macro to detect that the testcase
in comment 13 works. If that macro isn't defined, use the init function instead
of the init macro.

I'm not sure if/when I'll be able to work on that.


  parent reply	other threads:[~2012-01-11 16:50 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 18:08 [Bug libstdc++/51296] New: " ro at gcc dot gnu.org
2011-11-24 19:27 ` [Bug libstdc++/51296] " redi at gcc dot gnu.org
2011-11-24 20:30 ` redi at gcc dot gnu.org
2011-11-24 21:37 ` redi at gcc dot gnu.org
2011-11-25 14:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 14:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 14:47 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 15:17 ` redi at gcc dot gnu.org
2011-11-25 15:18 ` redi at gcc dot gnu.org
2011-11-25 15:21 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 15:22 ` redi at gcc dot gnu.org
2011-11-25 16:26 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-26 15:24 ` redi at gcc dot gnu.org
2011-11-26 16:03 ` redi at gcc dot gnu.org
2011-11-28 13:24 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-28 14:35 ` redi at gcc dot gnu.org
2011-11-28 14:40 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-28 15:10 ` redi at gcc dot gnu.org
2012-01-11 16:50 ` redi at gcc dot gnu.org [this message]
2012-01-11 17:38 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-11 17:49 ` redi at gcc dot gnu.org
2012-01-12 15:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-12 16:16 ` redi at gcc dot gnu.org
2012-01-12 18:18 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-13 10:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-13 10:54 ` redi at gcc dot gnu.org
2012-01-16 19:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-16 19:52 ` redi at gcc dot gnu.org
2012-01-31 12:48 ` ro at gcc dot gnu.org
2012-01-31 20:04 ` redi at gcc dot gnu.org
2012-02-01 10:24 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-01 10:59 ` redi at gcc dot gnu.org
2012-02-03  8:50 ` redi at gcc dot gnu.org
2012-02-03  8:52 ` redi at gcc dot gnu.org
2012-02-03  9:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-03  9:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-07  9:20 ` redi at gcc dot gnu.org
2012-02-07  9:23 ` redi at gcc dot gnu.org
2012-02-10 17:01 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-10 18:11 ` ro at gcc dot gnu.org
2012-02-10 18:14 ` ro 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-51296-4-qSg8WG2RHe@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).