From: Andrew Pinski <pinskia@physics.uc.edu>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org, Eliot Dresselhaus <edressel@cisco.com>
Subject: Re: bug w/ inline of inline?
Date: Mon, 18 Oct 2004 07:40:00 -0000 [thread overview]
Message-ID: <C1C74ECB-209C-11D9-B4B8-000A95D692F4@physics.uc.edu> (raw)
In-Reply-To: <877jposwsz.fsf@codesourcery.com>
On Oct 17, 2004, at 8:18 PM, Zack Weinberg wrote:
> Eliot Dresselhaus <edressel@cisco.com> writes:
>
>> In this example
>>
>> static inline int f (int x) { return x + 1; }
>>
>> static inline int g (int x, inline int f (int x))
>> { return 1 + f (x); }
>>
>> int h (int x)
>> { return g (x, f); }
>>
>> is h supposed to optimize to return x + 2 or supposed to actually call
>> f.
>
> GCC is allowed to do either. It would be good if it produced
> "return x + 2;" Please file a missed-optimization bug report.
We have one already, PR 9079: <http://gcc.gnu.org/PR9079>.
Thanks,
Andrew Pinski
a gcc bug master
next prev parent reply other threads:[~2004-10-18 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 4:48 Eliot Dresselhaus
2004-10-18 6:23 ` Zack Weinberg
2004-10-18 7:40 ` Andrew Pinski [this message]
2004-10-18 8:02 Richard Kenner
2004-10-18 19:28 ` Richard Henderson
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=C1C74ECB-209C-11D9-B4B8-000A95D692F4@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=edressel@cisco.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.com \
/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: link
Be 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).