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] readelf: Prune gaps in build notes


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.


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