This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Re: Fortran, committed: Forall-with-temporary problems(pr 50069 and pr 55086).
On 20 January 2017 at 00:27, Louis Krupp <louis.krupp@zoho.com> wrote:
> I was able to reproduce this on my x86 box by doing "make -k check". Apparently, "make check-fortran" wasn't enough to catch all of the consequences of changing gcc/fortran/lang.opt.
>
> The problem was the help text associated with the -ftest-forall-temp option; it needed to end with a period, and it didn't. I fixed that in revision 244657:
>
> ftest-forall-temp
> Fortran Var(flag_test_forall_temp) Init(0)
> -Force creation of temporary to test infrequently-executed forall code
> +Force creation of temporary to test infrequently-executed forall code.
>
Thanks for catching the typo, I didn't notice it.
I confirm the test now pass on my side.
Thanks for the prompt fix.
Christophe
> Louis
>
> ---- On Thu, 19 Jan 2017 04:52:54 -0800 Christophe Lyon wrote ----
>>Hi,
>>
>>
>>On 18 January 2017 at 22:45, Louis Krupp <louis.krupp@zoho.com> wrote:
>>> Fixed in revision 244601.
>>>
>>
>>I've noticed a new failure on arm/aarch64:
>> compiler driver --help=fortran option(s): "^ +-.*[^:.]$" absent from
>>output: " -ftest-forall-temp Force creation of temporary to
>>test infrequently-executed forall code"
>>when testing gcc. (I mean the error appears in gcc.sum/gcc.log, not
>>gfortran.sum)
>>
>>The output above the failure does contain:
>>[...]
>> -fstack-arrays Put all local arrays on stack.
>> -ftest-forall-temp Force creation of temporary to test
>>infrequently-executed forall code
>> -funderscoring Append underscores to externally visible names.
>>[...]
>>so I'm not sure why there is a failure?
>>
>>Christophe
>>
>>
>
>