Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Joel Sherrill
On 1/12/2015 3:18 PM, Tobias Burnus wrote: > Hi Joel, > > Am 12.01.2015 um 22:04 schrieb Joel Sherrill: >> That was very close. >> >> cat out.txt | \ >>perl -e '$in = join("", ); if ($in =~ m/^1 2 3(\n|\r\n|\r)1 2 >> 3(\n|\r\n|\r)((\n|\r\n|\r)\*\*\* EXIT code 0)(\n|\r\n|\r)?$/s) { print >> "

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Tobias Burnus
Hi Joel, Am 12.01.2015 um 22:04 schrieb Joel Sherrill: That was very close. cat out.txt | \ perl -e '$in = join("", ); if ($in =~ m/^1 2 3(\n|\r\n|\r)1 2 3(\n|\r\n|\r)((\n|\r\n|\r)\*\*\* EXIT code 0)(\n|\r\n|\r)?$/s) { print "matched\n" } else { print "not matched\n" };' That won't work

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Joel Sherrill
On 1/12/2015 2:49 PM, Tobias Burnus wrote: > Joel Sherrill wrote: >> run.txt is the cut and paste of the log file which reflects DejaGNU's >> view of the run. > Which means that it hopefully matches every bit of the original output > and that no editor interferes by adding or removing line break

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Tobias Burnus
Joel Sherrill wrote: run.txt is the cut and paste of the log file which reflects DejaGNU's view of the run. Which means that it hopefully matches every bit of the original output and that no editor interferes by adding or removing line breaks. Additionally, I think you are right that the "***

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Joel Sherrill
On 1/12/2015 1:14 PM, Tobias Burnus wrote: > Joel Sherrill wrote: >> On 1/12/2015 10:30 AM, Andreas Schwab wrote: >>> Joel Sherrill writes: >>> FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test, is 1 2 3 1 2 3 , should match ^1 2 3( | |)1 2 3(

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Tobias Burnus
Joel Sherrill wrote: On 1/12/2015 10:30 AM, Andreas Schwab wrote: Joel Sherrill writes: FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test, is 1 2 3 1 2 3 , should match ^1 2 3( | |)1 2 3( | |)$ Where is the \r gone? The pattern has (\n|\r\n|\r). I am not exactly sure wh

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Andreas Schwab
Joel Sherrill writes: > On 1/12/2015 10:30 AM, Andreas Schwab wrote: >> Joel Sherrill writes: >> >>> FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test, is 1 2 3 >>> 1 2 3 >>> >>> , should match ^1 2 3( >>> | >>> |)1 2 3( >>> | >>> |)$ >> Where is the \r gone? The pattern has

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Joel Sherrill
On 1/12/2015 10:30 AM, Andreas Schwab wrote: > Joel Sherrill writes: > >> FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test, is 1 2 3 >> 1 2 3 >> >> , should match ^1 2 3( >> | >> |)1 2 3( >> | >> |)$ > Where is the \r gone? The pattern has (\n|\r\n|\r). I am not exactly sure

Re: RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Andreas Schwab
Joel Sherrill writes: > FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test, is 1 2 3 > 1 2 3 > > , should match ^1 2 3( > | > |)1 2 3( > | > |)$ Where is the \r gone? The pattern has (\n|\r\n|\r). Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0

RTEMS FORTRAN Pattern Failures

2015-01-12 Thread Joel Sherrill
Hi RTEMS has pretty good FORTRAN test results on SPARC and PowerPC but a number fail in pattern matching. It appears to be a CR/LF issue. I have attached the output of f77-edit-x-out (out.txt) and the associated fragment (run.txt) from the test run log which shows the pattern not matching. Based