public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Andy Freeman" <anamax@earthlink.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/7269: Inlining may not eliminate unnecessary tests and branches. Date: Wed, 19 Feb 2003 14:56:00 -0000 [thread overview] Message-ID: <20030219145600.7193.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/7269; it has been noted by GNATS. From: "Andy Freeman" <anamax@earthlink.net> To: <ebotcazou@gcc.gnu.org>, <anamax@earthlink.net>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: optimization/7269: Inlining may not eliminate unnecessary tests and branches. Date: Wed, 19 Feb 2003 06:43:40 -0800 I'm no longer in a position to produce the code. The specific example looked like: struct foo { int f(int i) { ... // no branches or returns if( 0 = i ) { return 17; } ... } }; int bar(...) { foo f; if( f.f(0) ) { // the branch in f was eliminated by constant propagation .... // but the branch testing f's return value was not. } } ----- Original Message ----- From: <ebotcazou@gcc.gnu.org> To: <anamax@earthlink.net>; <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <nobody@gcc.gnu.org> Sent: Wednesday, February 19, 2003 1:26 AM Subject: Re: optimization/7269: Inlining may not eliminate unnecessary tests and branches. > Synopsis: Inlining may not eliminate unnecessary tests and branches. > > State-Changed-From-To: open->feedback > State-Changed-By: ebotcazou > State-Changed-When: Wed Feb 19 09:26:14 2003 > State-Changed-Why: > Sample code requested for 5 months. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7269
next reply other threads:[~2003-02-19 14:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-19 14:56 Andy Freeman [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-19 9:26 ebotcazou 2002-10-06 21:36 Andrew Pinski 2002-07-10 22:36 anamax
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=20030219145600.7193.qmail@sources.redhat.com \ --to=anamax@earthlink.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).