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] compiler misses opportunity to combine multiple identical function return paths Date: Thu, 10 May 2007 05:04:00 -0000 [thread overview] Message-ID: <20070510050439.15158.qmail@sourceware.org> (raw) In-Reply-To: <bug-31889-11337@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from raeburn at raeburn dot org 2007-05-10 06:04 ------- Created an attachment (id=13539) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13539&action=view) sample source code, with assembly & comments -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31889
next prev parent reply other threads:[~2007-05-10 5:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-10 5:04 [Bug rtl-optimization/31889] New: " raeburn at raeburn dot org 2007-05-10 5:04 ` raeburn at raeburn dot org [this message] 2007-05-10 6:13 ` [Bug rtl-optimization/31889] " steven at gcc dot gnu dot org 2007-05-10 21:25 ` raeburn at raeburn dot org [not found] <bug-31889-4@http.gcc.gnu.org/bugzilla/> 2012-01-28 2:25 ` pinskia at gcc dot gnu.org 2021-07-24 22:17 ` pinskia at gcc dot gnu.org 2023-09-03 3:44 ` 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=20070510050439.15158.qmail@sourceware.org \ --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).