Re: [PATCH] gfortran.dg/pr32627.f03 prints nul byte

2015-04-17 Thread msebor
Ping. Is this patch okay for trunk? On 04/09/2015 03:16 PM, Martin Sebor wrote: Attached is an updated patch that fixes the substr_6.f90 test that also prints a nul character to stdout. I don't think there are any others. Besides interfering with the debugging of the log corruption I

Re: [PATCH] gfortran.dg/pr32627.f03 prints nul byte

2015-04-17 Thread Jeff Law
On 04/17/2015 11:51 AM, mse...@redhat.com wrote: Ping. Is this patch okay for trunk? Yes, both are OK for the trunk. Sorry for the delay, we're really just getting started working through stuff that was queued up for stage1. jeff

[PATCH] gfortran.dg/pr32627.f03 prints nul byte

2015-04-09 Thread Martin Sebor
We've been debugging a problem where nul (and other control) characters have been randomly appearing in powerpc parallel build logs. In the process, I noticed that some of the nuls are readily reproducible. One such case is due to the pr32627.f03 test which verifies that Fortran programs can

Re: [PATCH] gfortran.dg/pr32627.f03 prints nul byte

2015-04-09 Thread Martin Sebor
Attached is an updated patch that fixes the substr_6.f90 test that also prints a nul character to stdout. I don't think there are any others. Besides interfering with the debugging of the log corruption I mentioned, printing nuls or control characters in tests is also problematic for tools