This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] Prune BFD warnings for unknown GNU properties
On Tue, Aug 21, 2018 at 9:51 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Tue, Aug 21, 2018 at 9:29 AM, Nick Clifton <nickc@redhat.com> wrote:
>> Hi H.J.
>>
>>>>> BFD will issue an unknown GNU property warning like
>>
>>>> So why not recognize that particular property, handle it
>>>> appropriately, and not warn?
>>
>>> It is OK for older binutils to ignore these new types. You just don't
>>> get new features with older binutils.
>>
>> True - but presumably you are not planning on backporting this patch
>> to anything other than the 2.31 branch ?
>
> That is correct.
>
>>
>>> And there may be new property types after
>>> binutils 2.32 is released.
>>
>> And new failures in the linker testsuite will help to alert us to these
>> new properties...
>>
>>
>>> "make check" will fail on binutils 2.32 branch.
>>> In fact, "make check" fails on binutils 2.31 branch.
>>
>> So in fact the question is whether we ought to allow tests on *branches*
>> to ignore unknown properties. On the grounds that they might be run on
>> machines with newer versions of glibc (or whatever else is producing
>> these notes).
>>
>> So - would it be possible to change your patch so that it is only
>> enabled if bfd/development.sh is set to false ?
>>
>
> development is set to false only during release. It was reset to true
> after release on binutils-2_31-branch branch. We need something
> similar to DEV-PHASE in GCC to indicate that this is a release branch.
>
A set of patches is posted at
https://sourceware.org/ml/binutils/2018-08/msg00378.html
--
H.J.