From: Dan Kegel <dank@kegel.com>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: profile-driven optimization and the linker?
Date: Thu, 25 Nov 2004 19:49:00 -0000 [thread overview]
Message-ID: <41A620F5.5040209@kegel.com> (raw)
http://gcc.gnu.org/news/profiledriven.html doesn't mention
having ld reorder sections to improve locality of reference
of frequently called functions. Has that technique
been tried with gcc and binutils?
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
next reply other threads:[~2004-11-25 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 19:49 Dan Kegel [this message]
2004-11-25 20:38 ` Jeffrey A Law
2004-11-25 21:07 ` Dan Kegel
2004-11-25 22:52 ` Joseph S. Myers
2004-11-26 5:32 ` Dan Kegel
2004-11-29 18:05 ` Joe Buck
2004-11-25 23:13 ` Jeffrey A Law
2004-11-26 5:08 ` Dan Kegel
2004-11-26 6:19 ` Dan Kegel
2004-11-26 8:55 ` Dan Kegel
2004-11-29 16:30 ` Will Cohen
2004-11-26 0:01 ` Ben Elliston
2004-11-29 16:20 ` Will Cohen
2004-11-30 3:24 ` Dan Kegel
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=41A620F5.5040209@kegel.com \
--to=dank@kegel.com \
--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).