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++/53578] include/ext/concurrence.h relies on ill-formed narrowing conversions Date: Fri, 29 Jun 2012 08:17:00 -0000 [thread overview] Message-ID: <bug-53578-4-NB7E8BrsNS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53578-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53578 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |WAITING --- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-06-29 08:17:21 UTC --- Ruben, any chance you could test trunk with clang? I'm not putting untested changes on the 4.6 and 4.7 release branches, so unless someone tests it on an affected platform and confirms it's fixed then it stays broken.
next prev parent reply other threads:[~2012-06-29 8:17 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-04 23:53 [Bug libstdc++/53578] New: " richard-gccbugzilla at metafoo dot co.uk 2012-06-04 23:55 ` [Bug libstdc++/53578] " pinskia at gcc dot gnu.org 2012-06-05 0:00 ` pinskia at gcc dot gnu.org 2012-06-05 0:05 ` paolo.carlini at oracle dot com 2012-06-05 0:24 ` redi at gcc dot gnu.org 2012-06-06 10:25 ` vanboxem.ruben at gmail dot com 2012-06-06 10:43 ` redi at gcc dot gnu.org 2012-06-06 10:46 ` redi at gcc dot gnu.org 2012-06-06 11:10 ` vanboxem.ruben at gmail dot com 2012-06-06 11:21 ` redi at gcc dot gnu.org 2012-06-15 0:27 ` redi at gcc dot gnu.org 2012-06-15 0:28 ` redi at gcc dot gnu.org 2012-06-15 0:29 ` redi at gcc dot gnu.org 2012-06-29 8:17 ` redi at gcc dot gnu.org [this message] 2012-06-29 14:16 ` internet at 123gen dot com 2012-07-07 18:13 ` redi at gcc dot gnu.org 2012-07-07 18:36 ` redi at gcc dot gnu.org 2012-07-07 18:36 ` redi at gcc dot gnu.org 2012-07-07 18:37 ` 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-53578-4-NB7E8BrsNS@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).