public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/45699] [4.6 Regression] Incorrect copy constructor generated with -O Date: Fri, 08 Oct 2010 14:41:00 -0000 [thread overview] Message-ID: <20101008144100.BBAq_CFG3SgXX_v8i-iDrGKpzDjRVNImMwg7xF45f9c@z> (raw) In-Reply-To: <bug-45699-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45699 --- Comment #7 from Martin Jambor <jamborm at gcc dot gnu.org> 2010-10-08 14:40:41 UTC --- Please disregard the previous comment, I saw what I wanted to see and not what was actually there. But it is true that avoiding the only O_T_R folding avoids the segfault. But so far I see nothing wrong with that devirtualization... I will keep staring at it for a bit longer.
next prev parent reply other threads:[~2010-10-08 14:41 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45699-4@http.gcc.gnu.org/bugzilla/> 2010-09-29 18:43 ` rguenth at gcc dot gnu.org 2010-10-06 15:46 ` bredelin at ucla dot edu 2010-10-08 12:12 ` jamborm at gcc dot gnu.org 2010-10-08 14:41 ` jamborm at gcc dot gnu.org [this message] 2010-10-08 15:59 ` bredelin at ucla dot edu 2010-10-08 16:37 ` bredelin at ucla dot edu 2010-10-08 16:51 ` jamborm at gcc dot gnu.org 2010-10-08 17:57 ` jamborm at gcc dot gnu.org 2010-10-11 18:45 ` jamborm at gcc dot gnu.org 2010-10-11 18:46 ` jamborm at gcc dot gnu.org 2010-09-17 0:50 [Bug middle-end/45699] New: " bredelin at ucla dot edu 2010-09-17 9:37 ` [Bug middle-end/45699] [4.6 Regression] " rguenth at gcc dot gnu dot org 2010-09-17 14:29 ` hjl dot tools at gmail dot com 2010-09-17 14:29 ` hjl dot tools at gmail dot com 2010-09-17 14:40 ` jamborm at gcc dot gnu dot 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=20101008144100.BBAq_CFG3SgXX_v8i-iDrGKpzDjRVNImMwg7xF45f9c@z \ --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).