From: Segher Boessenkool <segher@kernel.crashing.org>
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>
Cc: gcc@gcc.gnu.org, Richard Guenther <richard.guenther@gmail.com>
Subject: Re: GCC-4.0.2 20050811: should GCC consider inlining functions in between different sections?
Date: Tue, 16 Aug 2005 08:15:00 -0000 [thread overview]
Message-ID: <114d26722def3edd3510fa22e26923fa@kernel.crashing.org> (raw)
In-Reply-To: <20050812120551.89295.qmail@web26902.mail.ukl.yahoo.com>
> The question is in fact: what is a section for GCC? Is it just a way
> to
> group functions together to improve memory cache efficiency; or is the
> GCC user authorised to use sections to forbid access to some functions
> at link time?
For user-declared ("attribute") sections, GCC just outputs
the necessary assembler magic, and that's it. Anything else
is handled by your binary format tools, if at all.
Segher
prev parent reply other threads:[~2005-08-16 8:15 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
2005-08-16 8:15 ` Segher Boessenkool [this message]
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=114d26722def3edd3510fa22e26923fa@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=etienne_lorrain@yahoo.fr \
--cc=gcc@gcc.gnu.org \
--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).