This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Patch: RAM-based heuristics for ggc-min-heapsize and ggc-min-expand
- From: Mike Stump <mstump at apple dot com>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Cc: geoffk at geoffk dot org, Richard dot Earnshaw at arm dot com, gcc-patches at gcc dot gnu dot org
- Date: Thu, 13 Feb 2003 18:10:59 -0800
- Subject: Re: [RFC] Patch: RAM-based heuristics for ggc-min-heapsize and ggc-min-expand
On Thursday, February 13, 2003, at 05:59 PM, Kaveh R. Ghazi wrote:
I think the idea is that you'd get the info as part of the standard
bug report -v invocation. I.e.
cc1 -fpreprocessed -O2 -g -blah -blah ... -param ggc-min-heapsize=x
and you would automatically pass it back when reproducing the bug. If
we simply output the numbers with a printf then we have to teach
people new bug reporting and reproducing instructions cause they'd
have to gleen out and manually add these -param commands.
Ok?
I think the point is that be design, 99% of the time, it won't be
necessary to know or have that information to reproduce a bug. We can
put it in ggc-page (or where-ever) and if it really it a problem later,
it is possible to move it up.
Also, no, I disagree. The current instructions should encourage the
submitter to submit the output of -v. If -v shows the information,
then a bug reproducer/fixer can use that information, if they need it.
?