public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz> To: hubicka at ucw dot cz <gcc-bugzilla@gcc.gnu.org> Cc: gcc-bugs@gcc.gnu.org Subject: Re: [Bug tree-optimization/55823] [4.8 Regression] ice in inline_call, at ipa-inline-transform.c:270 Date: Wed, 02 Jan 2013 00:10:00 -0000 [thread overview] Message-ID: <20130102001028.GA15037@atrey.karlin.mff.cuni.cz> (raw) In-Reply-To: <bug-55823-4-4414wfuOsD@http.gcc.gnu.org/bugzilla/> ipa-cp is behaving funny here. It clones InitCommon so THIS pointer's binfo is known to enable devirtualization of SetLayoutDirection. It doesn't devirtualize GetLayoutDirection because it works on per-argument basis. This is stupid: obviously whenever THIS binfo is known also DC binfo is known, so we should propagate both into the clone. This is missed optimization relative to previous ipa-cp implementation and I think relatively serious one - it is very common that more than one argument is constant. Martin, can you take a look? Still don't know exactly why we miss the devirtualization after inlining. Honza
next prev parent reply other threads:[~2013-01-02 0:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-28 11:57 [Bug c++/55823] New: " dcb314 at hotmail dot com 2012-12-31 10:34 ` [Bug c++/55823] [4.8 Regression] " pinskia at gcc dot gnu.org 2012-12-31 11:57 ` [Bug tree-optimization/55823] " pinskia at gcc dot gnu.org 2013-01-01 23:32 ` Jan Hubicka 2012-12-31 12:01 ` pinskia at gcc dot gnu.org 2013-01-01 23:32 ` hubicka at ucw dot cz 2013-01-02 0:10 ` Jan Hubicka [this message] 2013-01-02 0:11 ` hubicka at ucw dot cz 2013-01-02 10:33 ` rguenth at gcc dot gnu.org 2013-01-03 16:23 ` hubicka at gcc dot gnu.org 2013-01-03 16:26 ` hubicka at gcc dot gnu.org 2013-01-08 20:23 ` hubicka at gcc dot gnu.org 2013-01-09 9:07 ` hubicka at gcc dot gnu.org 2013-01-09 9:33 ` 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=20130102001028.GA15037@atrey.karlin.mff.cuni.cz \ --to=hubicka@ucw.cz \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-bugzilla@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).