[PATCH] Make disabled-optimization warning more informative; increase default max-gcse-memory
Bradley Lucier
lucier@math.purdue.edu
Thu Nov 12 16:44:00 GMT 2015
This patch (a) removes an exact copy of is_too_expensive from cprop.c,
(b) renames is_too_expensive in gcse.c to
gcse_or_cprop_is_too_expensive, (c) expands the warning in
gcse_or_cprop_is_too_expensive to say how much --param max-gcse-memory
needs to be increased, and (d) increases the default max-gcse-memory
from 50MB to 128MB.
The expanded warning allowed me to see how much memory really was needed
to apply gcse to some of my routines, and 128MB fixes my problem. The
limit has been 50MB for over 10 years, I think we can up it a bit now.
Bootstrapped and checked, default languages, no regressions.
Brad
* gcc/cprop.c (is_too_expensive): Remove.
(gcse.h): Include.
(one_cprop_pass): Call gcse_or_cprop_is_too_expensive, not
is_too_expensive.
* gcc/gcse.h (gcse_or_cprop_is_too_expensive): Declare.
* gcc/gcse.c (is_too_expensive): Rename to ...
(gcse_or_cprop_is_too_expensive): ... this.
Expand warning to add required size of max-gcse-memory.
(one_pre_gcse_pass): Use it.
(one_code_hoisting_pass): Use it.
* gcc/params.def (max-gcse-memory): Increase from 50MB to 128MB.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcse.patch
Type: text/x-patch
Size: 5349 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20151112/447dd00b/attachment.bin>
More information about the Gcc-patches
mailing list