From: kai-gcc@khms.westfalen.de
To: gcc@gcc.gnu.org
Subject: Re: How to stop gcc from not calling noinline functions
Date: Sat, 12 Jan 2008 09:34:00 -0000 [thread overview]
Message-ID: <20080112082628.GA11975@desktop.khms.westfalen.de> (raw)
In-Reply-To: <200801120620.m0C6K3p1013168@ignucius.se.axis.com>
On Sat, Jan 12, 2008 at 07:20:03AM +0100, Hans-Peter Nilsson wrote:
> Or, another attribute. Name? Maybe "always_extern", but I'm
> not sure that's as intuitive and obvious as "noinline". I don't
> like the perhaps immediately obvious "always_call", because I
> think the calls should be deleted if the call-site is dead, just
> not for reasons found out from analysis of the called function,
> and the name suggests otherwise (alternatively, an implementation
> to stop dead-code elimination would be troublesome and useless. :)
volatile.
That seems to express exactly the right spirit: you can
dead-code-eliminate it, but if you don't, call it exactly as the source
code suggests.
I don't know if the language standards already associate an incompatible
meaning to it in this context; if so, just define an attribute with that
name.
next prev parent reply other threads:[~2008-01-12 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 8:26 Hans-Peter Nilsson
2008-01-12 9:34 ` kai-gcc [this message]
2008-01-12 10:24 ` Paolo Bonzini
2008-01-14 11:26 ` Hans-Peter Nilsson
2008-01-14 11:36 ` Dave Korn
2008-01-14 11:43 ` Jan Hubicka
2008-01-14 12:18 ` Hans-Peter Nilsson
2008-01-14 15:01 ` Dave Korn
2008-01-12 11:34 ` Richard Guenther
2008-02-06 23:59 ` Mark Mitchell
2008-02-07 1:19 ` Hans-Peter Nilsson
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=20080112082628.GA11975@desktop.khms.westfalen.de \
--to=kai-gcc@khms.westfalen.de \
--cc=gcc@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).