public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Mike Stump <mrs@apple.com>
Cc: Etienne Lorrain <etienne_lorrain@yahoo.fr>,
	Richard Guenther <richard.guenther@gmail.com>,
	gcc@gcc.gnu.org
Subject: Re: GCC-4.0.2 20050811: should GCC consider inlining functions in between different sections?
Date: Fri, 12 Aug 2005 17:27:00 -0000	[thread overview]
Message-ID: <20050812172701.GB11820@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <04652F75-2E4A-4B68-BD13-B52F7102A7CF@apple.com>

> On Aug 12, 2005, at 5:05 AM, Etienne Lorrain wrote:
> >  I have added a command to the linker file to forbid reference from
> > one section to another:
> >NOCROSSREFS (.text .xcode);
> 
> It sounds like this feature isn't compatible with inlining, -fno- 
> inline I suspect is one of the few ways to `fix' it in general, that,  
-fno-inline still won't suppress inlining of functions called once...

Honza
> or require that all functions be marked noinline that would otherwise  
> be wrong to inline.
> 
> >  The question is in fact: what is a section for GCC?
> 
> Anything a user wants.  We don't limit the uses, so this question  
> cannot, in general be answered, at best a few users could tell you  
> how a few of them are using sections.  For example, I would not  
> expect most people to know about NOCROSSREFS.

  reply	other threads:[~2005-08-12 17:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12 10:40 Etienne Lorrain
2005-08-12 11:07 ` Richard Guenther
2005-08-12 12:06   ` Etienne Lorrain
2005-08-12 17:10     ` Mike Stump
2005-08-12 17:27       ` Jan Hubicka [this message]
2005-08-16  8:15     ` Segher Boessenkool

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=20050812172701.GB11820@atrey.karlin.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=etienne_lorrain@yahoo.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=mrs@apple.com \
    --cc=richard.guenther@gmail.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).