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 c++/60750] double free after std::move on string inside throw when compiled with optimization
Date: Thu, 03 Apr 2014 18:12:00 -0000 [thread overview]
Message-ID: <bug-60750-4-B6gsQexiLR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60750-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60750
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|x86_64-unknown-linux-gnu |
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-04-03
Host|Linux hostname |
|3.2.0-29-generic #46-Ubuntu |
|SMP Fri Jul 27 17:03:23 UTC |
|2012 x86_64 x86_64 x86_64 |
|GNU/Linux |
Ever confirmed|0 |1
Build|../gcc-4.8.2/configure |
|--disable-multilib |
|--enable-languages=c++ |
|--program-suffix=-4.8.2 |
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to sshannin from comment #0)
> I considered this source small enough (with standard headers) to not require
> the preprocessed to be attached.
Yep, it's fine, thanks.
Preprocessed source compiles and runs OK with clang, so I don't think it's a
library bug.
next prev parent reply other threads:[~2014-04-03 18:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 15:51 [Bug c++/60750] New: " sshannin at gmail dot com
2014-04-03 18:12 ` redi at gcc dot gnu.org [this message]
2014-04-03 18:19 ` [Bug c++/60750] " trippels at gcc dot gnu.org
2014-04-03 19:41 ` sshannin at gmail dot com
2014-04-04 9:43 ` [Bug c++/60750] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2014-04-04 11:00 ` trippels at gcc dot gnu.org
2014-04-04 11:22 ` rguenth at gcc dot gnu.org
2014-04-04 11:37 ` rguenth at gcc dot gnu.org
2014-04-04 12:14 ` rguenth at gcc dot gnu.org
2014-04-07 8:39 ` rguenth at gcc dot gnu.org
2014-04-07 8:39 ` [Bug c++/60750] [4.8 " rguenth at gcc dot gnu.org
2014-05-05 13:49 ` rguenth at gcc dot gnu.org
2014-05-05 13:50 ` rguenth 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-60750-4-B6gsQexiLR@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).