On Wed, 2020-06-10 at 23:41 -0300, Alexandre Oliva wrote:
> On May 26, 2020, Alexandre Oliva <ol...@adacore.com> wrote:
>
> > On May 19, 2020, Joseph Myers <jos...@codesourcery.com> wrote:
> > > Allowing a missing executable name is reasonable enough, but I was
> > > actually thinking that the messages should print "gcc" or whatever
> > > command
> > > the user ran in place of "collect2".
> > Should we make the regexps '\[^\n\]*', as in so many other pruned
> > messages?
>
> Like this. Regstrapped on x86_64-linux-gnu. Ok to install?
>
>
> match any program name when pruning collect messages
>
> From: Alexandre Oliva <ol...@adacore.com>
>
> When collect* programs have an executable suffix, they may include it
> in their outputs. Match them when pruning gcc output, making room for
> other program names to print them.
>
>
> for gcc/testsuite/ChangeLog
>
> * lib/prune.exp (prune_gcc_output): Match any executable name
> in collect messages.
OK
jeff
>
