public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "raeburn at raeburn dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/31889] New: compiler misses opportunity to combine multiple identical function return paths Date: Thu, 10 May 2007 05:04:00 -0000 [thread overview] Message-ID: <bug-31889-11337@http.gcc.gnu.org/bugzilla/> (raw) The source file I'm submitting has two implementations of an inline function, and a second function which calls it and then prints one of two strings depending on the return value. With the simpler implementation of the inline function, one call to puts() is followed by a jump to the return sequence emitted after the other puts() call. With the more complicated (but functionally equivalent) implementation of the inline function, the caller's two paths aren't combined; two sets of instructions are emitted to restore the same registers from the same stack slots before returning. It should still be able to combine them. (A second possible missed optimization? The branch could've been done to the puts call, instead of to just after, saving one call instruction. Unless a branch to a call is slower than a call that returns to a branch instruction on these processors.) -- Summary: compiler misses opportunity to combine multiple identical function return paths Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: raeburn at raeburn dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31889
next reply other threads:[~2007-05-10 5:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-10 5:04 raeburn at raeburn dot org [this message] 2007-05-10 5:04 ` [Bug rtl-optimization/31889] " raeburn at raeburn dot org 2007-05-10 6:13 ` steven at gcc dot gnu dot org 2007-05-10 21:25 ` raeburn at raeburn dot 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-31889-11337@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).