This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] readelf: Prune gaps in build notes
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Binutils <binutils at sourceware dot org>
- Date: Tue, 20 Nov 2018 06:41:08 -0800
- Subject: Re: [PATCH] readelf: Prune gaps in build notes
- References: <20181119204848.3858-1-hjl.tools@gmail.com>
On Mon, Nov 19, 2018 at 12:49 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> Since not all files have build notes, it is normal to have gaps in build
> notes.
>
> PR binutils/23898
> * testsuite/lib/binutils-common.exp (prune_warnings_extra):
> Prune gaps in build notes.
> ---
> binutils/testsuite/lib/binutils-common.exp | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/binutils/testsuite/lib/binutils-common.exp b/binutils/testsuite/lib/binutils-common.exp
> index f1a153193c..bbbbfbe8ad 100644
> --- a/binutils/testsuite/lib/binutils-common.exp
> +++ b/binutils/testsuite/lib/binutils-common.exp
> @@ -442,6 +442,8 @@ proc prune_warnings_extra { text } {
> # The "\\1" is to try to preserve a "\n" but only if necessary.
> regsub -all "(^|\n)(\[^\n\]*: warning:\[^\n\]*unsupported GNU_PROPERTY_TYPE\[^\n\]*\n?)+" $text "\\1" text
> }
> + # PR binutils/23898: It is OK to have gaps in build notes.
> + regsub -all "(^|\n)(\[^\n\]*: Warning: Gap in build notes detected from\[^\n\]*\n?)+" $text "\\1" text
> return $text
> }
>
> --
> 2.19.1
>
I am checking it in.
--
H.J.