Re: Report DejaGnu ERROR messages in dg-extract-results

2016-09-23 Thread Christophe Lyon
On 23 September 2016 at 13:37, Rainer Orth wrote: > Hi Christophe, > >> We recently faced a problem where a DejaGnu error went un-noticed >> (https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01879.html). > > I just noticed that your patch contained an unrelated and

Re: Report DejaGnu ERROR messages in dg-extract-results

2016-09-23 Thread Rainer Orth
Hi Christophe, > We recently faced a problem where a DejaGnu error went un-noticed > (https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01879.html). I just noticed that your patch contained an unrelated and bogus change, reverted as follows. This will only show up on targets that lack (a

Re: Report DejaGnu ERROR messages in dg-extract-results

2016-09-20 Thread Jeff Law
On 09/20/2016 03:26 AM, Christophe Lyon wrote: Hello, We recently faced a problem where a DejaGnu error went un-noticed (https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01879.html). To help identify these problems earlier, here is a patch for dg-extract-results that makes such error obvious in