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 tree-optimization/45791] Missed devirtualization Date: Thu, 07 Jan 2021 17:38:56 +0000 [thread overview] Message-ID: <bug-45791-4-D35zlF0dYZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45791-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45791 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #18 from Martin Jambor <jamborm at gcc dot gnu.org> --- The release_ssa dump of function main in the testcase from bug description is just "return 0;" The release_ssa dump of function main the testcase from comment #15 is: int main () { <bb 2> [local count: 1073741824]: Sub::bar (&foo); Sub::bar (&foo); return 0; } ...so devirtualized in my book (main is cold, so they are not inlined, of course). The release_ssa dump of function foo in the testcase from comment #5 is: void foo () { void * _3; <bb 2> [local count: 1073741824]: _3 = operator new (8); MEM[(struct X *)_3]._vptr.X = &MEM <int (*) ()[4]> [(void *)&_ZTV1X + 16B]; X::~X (_3); return; } ...so also devirtualzied before IPA. Therefore I am going to close this old bug as done. If anyone finds a different testcase where the early optimizers should do a better job to help devirtualziation, please file a new bug.
prev parent reply other threads:[~2021-01-07 17:38 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-25 17:28 [Bug tree-optimization/45791] New: " hubicka at gcc dot gnu.org 2010-09-25 19:50 ` [Bug tree-optimization/45791] " hubicka at gcc dot gnu.org 2010-09-26 3:33 ` hubicka at gcc dot gnu.org 2010-09-26 3:39 ` hubicka at gcc dot gnu.org 2010-09-26 6:02 ` hubicka at gcc dot gnu.org 2010-10-11 17:15 ` jamborm at gcc dot gnu.org 2010-10-11 18:40 ` jamborm at gcc dot gnu.org 2010-12-14 17:46 ` jamborm at gcc dot gnu.org 2010-12-14 23:15 ` hubicka at gcc dot gnu.org 2010-12-14 23:17 ` hubicka at gcc dot gnu.org 2010-12-14 23:35 ` jamborm at gcc dot gnu.org 2010-12-15 0:10 ` hubicka at gcc dot gnu.org 2010-12-15 0:13 ` hubicka at gcc dot gnu.org 2010-12-15 16:07 ` jamborm at gcc dot gnu.org 2014-02-24 9:44 ` matthijs at stdin dot nl 2014-09-25 20:29 ` hubicka at gcc dot gnu.org 2021-01-07 17:38 ` jamborm at gcc dot gnu.org [this message]
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-45791-4-D35zlF0dYZ@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).