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++/55449] [4.4.3] pure virtual call only with -O1/2/3 (boost::optional) Date: Sat, 24 Nov 2012 14:21:00 -0000 [thread overview] Message-ID: <bug-55449-4-lP8zvw2aj1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55449-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55449 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.5.0 --- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-11-24 14:21:12 UTC --- (In reply to comment #8) > Jonathan, I have nothing against you personaly, what you wrote is: > > "GCC 4.4 is no longer supported, and the problem *seems* to be already fixed in > current releases." > > and doesn't exactly show that you have investigate, I have also stated that > with 4.7.3 works. I investigated and couldn't find anything conclusive, so I said "seems" because I wasn't certain. If you assume I didn't investigate and reply with "time to adopt ICC" then feel free to do so, I don't volunteer my time to GCC for people with that attitude. > Actualy the code I have submitted was tailored already I couldn't shrink more > than I did. To be honest with the real code instead to have a "pure virtual > call" I had a simple core with gdb finding bogus data in the core, that was the > smallest test I was able to make it reproducible. http://gcc.gnu.org/bugs/minimize.html http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction > About the fact I didn't post the g++ -v output you are right, I have issued the > command "g++ -v -save-temps ..." but somehow the output get lost in the archive > attached. If you are interested in the output I will provide it. I'm not interested, the point is you provided an incomplete bug report but are then happy to complain about the effort put in by people who look at it. The bug was fixed by http://gcc.gnu.org/ml/gcc-cvs/2009-04/msg00115.html so is fixed in 4.5.0 and later
next prev parent reply other threads:[~2012-11-24 14:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-23 15:44 [Bug c++/55449] New: " mendola at gmail dot com 2012-11-23 16:06 ` [Bug c++/55449] " redi at gcc dot gnu.org 2012-11-23 16:11 ` paolo.carlini at oracle dot com 2012-11-24 6:28 ` mendola at gmail dot com 2012-11-24 6:37 ` pinskia at gcc dot gnu.org 2012-11-24 6:57 ` mendola at gmail dot com 2012-11-24 9:43 ` paolo.carlini at oracle dot com 2012-11-24 12:03 ` redi at gcc dot gnu.org 2012-11-24 12:25 ` mendola at gmail dot com 2012-11-24 14:21 ` redi at gcc dot gnu.org [this message] 2012-11-24 17:49 ` mendola at gmail dot com
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-55449-4-lP8zvw2aj1@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).