public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "takis at issaris dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/29782] Incorrect inlining failure
Date: Thu, 09 Nov 2006 17:28:00 -0000 [thread overview]
Message-ID: <20061109172836.2993.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29782-12207@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from takis at issaris dot org 2006-11-09 17:28 -------
(In reply to comment #3)
> It has a heuristic to tell the result in code-size difference. Of course no
> heuristic is perfect - see tree-inline.c:estimate_num_insns().
Ofcourse! Thanks for your reply!
So, I guess that if I were to move ASM_EXPR to the list of zero cost cases, GCC
would always inline my code. I'll see if this works. Thanks again! :)
Still, I think it is weird I'm seeing this behavior, as with my untrained eyes,
it seems as if inline assembly would only get 1 assigned as cost, while a
function call probably costs 4+something (I guess from estimate_move_cost()
although it can also return another value of which I am currently not capable
of determining the value). This would mean inlining of functions containing
only inline assembly blocks would always succeed, right? Hmm... Unless the else
in estimate_move_cost() can return 0 or 1 in some cases.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29782
next prev parent reply other threads:[~2006-11-09 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 16:30 [Bug c/29782] New: " takis at issaris dot org
2006-11-09 16:31 ` [Bug c/29782] " takis at issaris dot org
2006-11-09 16:32 ` takis at issaris dot org
2006-11-09 17:11 ` [Bug middle-end/29782] " rguenth at gcc dot gnu dot org
2006-11-09 17:28 ` takis at issaris dot org [this message]
2006-11-09 17:31 ` pinskia at gcc dot gnu dot org
2007-04-08 22:46 ` pinskia 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=20061109172836.2993.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: 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).