From: Ian Lance Taylor <iant@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
Date: Tue, 17 May 2011 15:02:00 -0000 [thread overview]
Message-ID: <mcrvcx9xte0.fsf@coign.corp.google.com> (raw)
In-Reply-To: <BANLkTin3tbwZ4D9KDSxYCDTGFyw1jGSa6g@mail.gmail.com> (H. J. Lu's message of "Tue, 17 May 2011 07:35:56 -0700")
"H.J. Lu" <hjl.tools@gmail.com> writes:
>> The difference is that the author of a shared library can call a
>> function with a warning safely from another externally visible function
>> which does not require a warning.
>>
>
> How does linker know warning is from the author of a shared library.
> A shared library may contain many 3rd party objects.
Sure, but it's hardly the common case.
Ian
next prev parent reply other threads:[~2011-05-17 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 19:05 H.J. Lu
2011-05-17 1:51 ` Alan Modra
2011-05-17 6:04 ` Ian Lance Taylor
2011-05-17 13:12 ` H.J. Lu
2011-05-17 14:30 ` Ian Lance Taylor
2011-05-17 14:36 ` H.J. Lu
2011-05-17 15:02 ` Ian Lance Taylor [this message]
2011-05-17 15:05 ` H.J. Lu
2011-05-17 16:34 ` Ian Lance Taylor
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=mcrvcx9xte0.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@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).