public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/63140] wrong code generation probably due to optimization problem Date: Wed, 03 Sep 2014 16:35:00 -0000 [thread overview] Message-ID: <bug-63140-4-aosWmhONcP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63140-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63140 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> --- With that reduced testcase, I've bisected it to r208831, before inlining pass there are no differences, and starting with r208831 the inliner changes 3 calls to __builtin_unreachable - __dynamic_cast, AWindow2::isParent and fwrite. Haven't yet looked why the inliner considers those unreachable, if there is some undefined behavior that makes those unreachable, or something else. Honza?
next prev parent reply other threads:[~2014-09-03 16:35 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-02 15:51 [Bug c++/63140] New: " gcc at boomerangsworld dot de 2014-09-02 15:54 ` [Bug c++/63140] " gcc at boomerangsworld dot de 2014-09-02 17:54 ` gcc at boomerangsworld dot de 2014-09-03 9:03 ` rguenth at gcc dot gnu.org 2014-09-03 9:45 ` jakub at gcc dot gnu.org 2014-09-03 10:30 ` gcc at boomerangsworld dot de 2014-09-03 12:12 ` jakub at gcc dot gnu.org 2014-09-03 12:57 ` gcc at boomerangsworld dot de 2014-09-03 12:59 ` gcc at boomerangsworld dot de 2014-09-03 13:00 ` gcc at boomerangsworld dot de 2014-09-03 13:01 ` gcc at boomerangsworld dot de 2014-09-03 13:05 ` gcc at boomerangsworld dot de 2014-09-03 16:35 ` jakub at gcc dot gnu.org [this message] 2021-07-22 16:50 ` pinskia 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-63140-4-aosWmhONcP@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).