On Tue, Nov 19, 2019 at 12:36 PM Martin Liška <mli...@suse.cz> wrote: > > On 11/19/19 10:12 AM, Richard Biener wrote: > > On Tue, Nov 19, 2019 at 9:12 AM Martin Liška <mli...@suse.cz> wrote: > >> > >> One potential improvement is to enable the heuristics > >> for ENABLE_GC_CHECKING. The macro is about sanity checking > >> and poisoning of GGC memory. Which seems to me completely > >> independent to setting of the default parameters. > > > > Well, doing more collects also is "checking" and the GC checking part > > this way becomes deterministic (not dependent on host setup) so no, > > this is by no means an obvious change. If we think we collect too > > often we can adjust the GC param static defaults to todays reality instead > > (mostly --param ggc-min-heapsize which has been 4MB for ages). > > Sure, that's probably more reasonable change we can do. Do you have a > suggestion > when can default be now?
I'm not sure. For GC checking (poisoning, etc.) more collecting is better because then stuff is poisoned earlier. The question is really the intent here. > > > > Btw, I see the params.opt default is now 4096 unconditionally so > > does ENABLE_GC_ALWAYS_COLLECT no longer "work"? > > It used to adjust the params.def default values. > > It will work with ENABLE_GC_ALWAYS_COLLECT once the patch > in previous email will be applied. > > Martin > > > > > Richard. > > > >> Ready to be installed? > >> Thanks, > >> Martin >
