public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/58208] deque<std::string> 32-bit "-O3" bug Date: Wed, 07 Jun 2023 02:05:30 +0000 [thread overview] Message-ID: <bug-58208-4-RfsHf1hPkC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58208-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |MOVED --- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This was a glibc issue. Fixed by glibc commit 5e49c52efdb37eb0aa315156f39056f25ff9ddaa ( https://sourceware.org/git/?p=glibc.git;a=commit;h=5e49c52efdb37eb0aa315156f39056f25ff9ddaa )
next prev parent reply other threads:[~2023-06-07 2:05 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-20 22:28 [Bug c++/58208] New: " tammy at Cadence dot COM 2013-08-20 22:38 ` [Bug tree-optimization/58208] " paolo.carlini at oracle dot com 2013-08-23 22:34 ` [Bug target/58208] " tammy at Cadence dot COM 2013-08-23 23:05 ` pinskia at gcc dot gnu.org 2013-08-24 12:19 ` mikpe at it dot uu.se 2013-08-25 10:14 ` mikpe at it dot uu.se 2013-08-25 18:12 ` mikpe at it dot uu.se 2013-08-25 20:02 ` mikpe at it dot uu.se 2013-08-26 3:07 ` tammy at Cadence dot COM 2013-08-26 17:08 ` tammy at Cadence dot COM 2013-08-26 19:43 ` tammy at Cadence dot COM 2013-08-28 23:02 ` tammy at Cadence dot COM 2023-06-07 2:03 ` pinskia at gcc dot gnu.org 2023-06-07 2:05 ` pinskia at gcc dot gnu.org [this message] 2023-06-07 2:06 ` pinskia 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-58208-4-RfsHf1hPkC@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).