On Nov 12, 2014, at 6:09 AM, Marek Polacek wrote:
> The following patch moves the path prunning code into a separate
> procedure and fixes the failures.
>
> Ok for trunk?
Ok.
On 12/11/14 14:09, Marek Polacek wrote:
... prune_gcc_output prunes more than just absolute file paths, it
prunes even the "note: " messages. And several ubsan tests have
/* { dg-output "\[^\n\r]*note: pointer points here\[^\n\r]*(\n|\r\n|\r)" } */
but since the note's are already gone, the te
On Tue, Nov 11, 2014 at 04:51:38PM +, Jiong Wang wrote:
> currently, only sanitizer tess (asan/tsan/ubsan) and a couple of fortran test
> will invoke dg-output.
>
> pass x86-64 c/c++ regression.
> pass aarch64-none-linux-gnu c/c++ regression.
This patch broke a few tests in ubsan.exp. The r
On Nov 11, 2014, at 8:51 AM, Jiong Wang wrote:
> currently, if a testcase use dg-output, then absolute file path will occur
> in the test summary reported by dejagnu which is bad.
> ok for trunk?
Ok.
currently, if a testcase use dg-output, then absolute file path will occur
in the test summary reported by dejagnu which is bad. because the summary
should only contain the test name and it's better to exclude all local test
machine info from the report.
dg-output eventually calls dejagnu generic
