public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/60965] [4.10 Regression] IPA: Devirtualization versus placement new Date: Sat, 03 May 2014 18:05:00 -0000 [thread overview] Message-ID: <bug-60965-4-Ut7fhZ1vfg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60965-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60965 Harald van Dijk <harald at gigawatt dot nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harald at gigawatt dot nl --- Comment #10 from Harald van Dijk <harald at gigawatt dot nl> --- (In reply to Jan Hubicka from comment #4) > Mine, probably 4.9 regression, too. It is, and Jonathan Wakely's earlier reduction exposes it on 4.9 too. (In reply to Jan Hubicka from comment #6) > Can you, please, double check that it fixes the Java issues? With 4.9.0, for me, IcedTea reliably hangs during the build process. I hadn't investigated the problem at all, but with 4.9.0 plus your patch, it builds successfully. What I had looked into was a segmentation fault in Qt (https://bugreports.qt-project.org/browse/QTBUG-38733) and Chromium, both using WebKit, also because of this. Chromium is still building, but for Qt, I can confirm it is also fixed by your patch. (In reply to Jason Merrill from comment #9) > As far as I know people always use char arrays for placement new anyway; at > least all the examples I've ever seen do. Or a structure containing (possibly indirectly) a character array as its first member, such as aligned_storage. But as long as a pointer to such a structure is indistinguishable from a pointer to the contained character array, that should not be a problem.
next prev parent reply other threads:[~2014-05-03 18:05 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-25 13:35 [Bug c++/60965] New: " aph at gcc dot gnu.org 2014-04-25 14:24 ` [Bug ipa/60965] " aph at gcc dot gnu.org 2014-04-25 14:59 ` [Bug ipa/60965] [4.10 Regression] " redi at gcc dot gnu.org 2014-04-25 15:51 ` jamborm at gcc dot gnu.org 2014-04-25 16:28 ` hubicka at gcc dot gnu.org 2014-04-28 9:53 ` rguenth at gcc dot gnu.org 2014-04-30 7:51 ` aph at gcc dot gnu.org 2014-05-01 9:40 ` hubicka at gcc dot gnu.org 2014-05-02 19:18 ` jason at gcc dot gnu.org 2014-05-03 9:42 ` aph at gcc dot gnu.org 2014-05-03 13:21 ` jason at gcc dot gnu.org 2014-05-03 18:05 ` harald at gigawatt dot nl [this message] 2014-05-04 10:01 ` aph at gcc dot gnu.org 2014-05-04 12:13 ` hubicka at ucw dot cz 2014-05-04 12:17 ` hubicka at ucw dot cz 2014-05-05 19:41 ` hubicka at gcc dot gnu.org 2014-05-05 23:28 ` hubicka 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-60965-4-Ut7fhZ1vfg@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).