From: Richard Guenther <richard.guenther@gmail.com>
To: Bingfeng Mei <bmei@broadcom.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: externally_visible and resoultion file
Date: Wed, 26 May 2010 16:19:00 -0000 [thread overview]
Message-ID: <AANLkTimYbuzLlapl78bxFsRaj93klV8_cAzJLhPCKPcS@mail.gmail.com> (raw)
In-Reply-To: <7FB04A5C213E9943A72EE127DB74F0ADA6666C4CB4@SJEXCHCCR02.corp.ad.broadcom.com>
On Wed, May 26, 2010 at 5:53 PM, Bingfeng Mei <bmei@broadcom.com> wrote:
> Hi, Richard,
> With resolution file generated by GOLD (or I am going to hack gnu LD), is
> externally_visible attribute still needed to annotate those symbols accessed
> from non-LTO objects when compiling with -fwhole-program.
Yes it is. We do not parse the complete resolution file but only the
entries we'll end up reading .o files with LTO information for.
> In theory, it shouldn't be needed since LTO has all information. But what
> about current implementation. I checked relevant source files and can't
> get immediate clue.
The current implementation has no idea of the external references
(though it's probably not too hard to implement).
Richard.
next prev parent reply other threads:[~2010-05-26 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 16:03 Bingfeng Mei
2010-05-26 16:19 ` Richard Guenther [this message]
2010-05-27 8:10 ` Jan Hubicka
2010-06-08 13:48 ` Bingfeng Mei
2010-06-08 14:05 ` Richard Guenther
2010-06-08 14:22 ` Bingfeng Mei
2010-06-08 14:22 ` Richard Guenther
2010-06-08 14:58 ` Bingfeng Mei
2010-06-08 14:59 ` Richard Guenther
2010-06-09 20:46 ` Cary Coutant
2010-06-10 2:29 ` Richard Guenther
2010-06-10 11:57 ` Bingfeng Mei
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=AANLkTimYbuzLlapl78bxFsRaj93klV8_cAzJLhPCKPcS@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=bmei@broadcom.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).