This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library

From: Ian Lance Taylor <iant at google dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: binutils at sourceware dot org
Date: Tue, 17 May 2011 08:02:15 -0700
Subject: Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
References: <20110516190512.GA10653@intel.com> <mcrsjsd278z.fsf@coign.corp.google.com> <BANLkTin3aehZppucE8Rr9DUhjHPmZCQnDw@mail.gmail.com> <mcrd3jhz9fg.fsf@coign.corp.google.com> <BANLkTin3tbwZ4D9KDSxYCDTGFyw1jGSa6g@mail.gmail.com>

"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

Follow-Ups:
- Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
  - From: H.J. Lu

References:
- PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
  - From: H.J. Lu
- Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
  - From: Ian Lance Taylor
- Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
  - From: H.J. Lu
- Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
  - From: Ian Lance Taylor
- Re: PATCH: PR ld/12761: .gnu.warning.* doesn't work when building shared library
  - From: H.J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]