public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59470] [4.8 Regression] libstdc++ miscompilation after r205709
Date: Thu, 12 Dec 2013 15:39:00 -0000	[thread overview]
Message-ID: <bug-59470-4-vMjwsZfAKo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59470-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #13)
> Strange.  From my limited testing, it does fix the regressions.  I can fire
> off now full scratch rpm builds with your patch.

Sorry. My bad. I did not rebuild the library (I rebuilt only compiler) when I
tested it.

In general, the probability of this bug is quite tiny so many conditions must
come up for this.  That is why we found it only recently.  Thanks for working
on it, Jakub.  Your analysis helped me a lot.  You can commit it into gcc-4.8
and gcc-4.9.


  parent reply	other threads:[~2013-12-12 15:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 14:14 [Bug middle-end/59470] New: " jakub at gcc dot gnu.org
2013-12-11 14:14 ` [Bug middle-end/59470] " jakub at gcc dot gnu.org
2013-12-11 14:15 ` jakub at gcc dot gnu.org
2013-12-11 14:15 ` jakub at gcc dot gnu.org
2013-12-11 14:32 ` rguenth at gcc dot gnu.org
2013-12-11 14:35 ` hjl.tools at gmail dot com
2013-12-11 14:37 ` jakub at gcc dot gnu.org
2013-12-11 14:42 ` hjl.tools at gmail dot com
2013-12-11 15:52 ` jakub at gcc dot gnu.org
2013-12-11 16:28 ` jakub at gcc dot gnu.org
2013-12-11 18:24 ` jakub at gcc dot gnu.org
2013-12-11 18:43 ` jakub at gcc dot gnu.org
2013-12-11 19:46 ` jakub at gcc dot gnu.org
2013-12-12  2:00 ` vmakarov at gcc dot gnu.org
2013-12-12  2:01 ` vmakarov at gcc dot gnu.org
2013-12-12  7:14 ` jakub at gcc dot gnu.org
2013-12-12  7:49 ` rguenther at suse dot de
2013-12-12  9:54 ` jakub at gcc dot gnu.org
2013-12-12 13:26 ` jakub at gcc dot gnu.org
2013-12-12 15:39 ` vmakarov at gcc dot gnu.org [this message]
2013-12-12 15:41 ` jakub at gcc dot gnu.org
2013-12-12 15:48 ` vmakarov at gcc dot gnu.org
2013-12-12 15:51 ` vmakarov at gcc dot gnu.org
2013-12-12 17:56 ` jakub at gcc dot gnu.org
2013-12-16  8:09 ` jakub at gcc dot gnu.org
2014-01-07 16:49 ` jakub at gcc dot gnu.org
2014-01-07 16:52 ` jakub at gcc dot gnu.org
2014-01-08 10:16 ` hp 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-59470-4-vMjwsZfAKo@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).