public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38629] target-specific parameters for inline heuristics not defined for AVR
Date: Wed, 10 Nov 2010 20:19:00 -0000 [thread overview]
Message-ID: <bug-38629-4-7JE7aBjhwf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38629-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38629
--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> 2010-11-10 20:19:24 UTC ---
Hi,
I have reservations for making inline heuristics too target specific as it
would increase the testing matrix of inliner even more. It is difficult to
satisfy everyone.
We no longer inline delay_wait_us on i386, ARM should behave the same. For
whatever reason we still inline delay_wait_us_ms. I am checking why. Size is
estimated to grow by one instruction (that is bit underestimated) but with
--param early-inlining-insns=0 we should not inline.
Honza
next parent reply other threads:[~2010-11-10 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-38629-4@http.gcc.gnu.org/bugzilla/>
2010-11-10 20:19 ` hubicka at gcc dot gnu.org [this message]
2010-11-10 20:52 ` hubicka at gcc dot gnu.org
2015-04-09 15:43 ` federico at fsfe dot org
2015-04-09 15:47 ` federico at fsfe dot org
2008-12-26 14:58 [Bug c/38629] New: gcc version 4.2.x, 4.3.x and 4.4.0 are doing (too much) automatic inlining with -O1, -O2 and -Os cbm at d81 dot de
2008-12-26 15:41 ` [Bug target/38629] target-specific parameters for inline heuristics not defined for AVR steven at gcc dot gnu dot org
2008-12-26 21:30 ` forwards dot from dot bugzilla at d81 dot de
2008-12-26 21:36 ` pinskia at gcc dot gnu dot org
2008-12-29 20:14 ` rguenth at gcc dot gnu 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-38629-4-7JE7aBjhwf@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: 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).