On 05/04/2011 02:00 PM, Tobias Burnus wrote:
As the example in the PR shows, using -fno-protect parens can make a
huge difference. As -fno-protect is in the spirit of -Ofast, enable it
with that option.
As long as -Ofast -fprotect-parens still works, I don't think this would
be objectionable.
On 05/04/2011 06:43 PM, Thomas Koenig wrote:
Out of curiosity: Why do you do
gfc_option.flag_protect_parens = optimize_fast ? 0 : 1;
instead of
gfc_option.flag_protect_parens = optimize_fast;
I found it more clearer than = !optimize_fast (note the "!"), but
that's seemingly not the case.
Hi Tobias,
As the example in the PR shows, using -fno-protect parens can make a
huge difference. As -fno-protect is in the spirit of -Ofast, enable it
with that option.
Build on x86-64-linux.
OK for the trunk?
OK.
Out of curiosity: Why do you do
gfc_option.flag_protect_parens = optimize_fas
As the example in the PR shows, using -fno-protect parens can make a
huge difference. As -fno-protect is in the spirit of -Ofast, enable it
with that option.
Build on x86-64-linux.
OK for the trunk?
Tobias
gcc/
2011-05-04 Tobias Burnus
PR fortran/48864
* doc/invoke.texi (Ofast): Document
