This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Patch: RAM-based heuristics for ggc-min-heapsize and ggc-min-expand


> Date: Sat, 15 Feb 2003 20:33:04 -0500 (EST)
> From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>

>  > From: Richard Henderson <rth@redhat.com>
>  > 
>  > On Sat, Feb 15, 2003 at 11:24:32AM -0500, Kaveh R. Ghazi wrote:
>  > > 1.  One of Geoff or Richard needs to withdraw their objections to the
>  > >     implementation approach and I possibly need to rewrite it to live
>  > >     in gcc.c instead of cc1 if that's the agreed upon choice (or leave
>  > >     it as-is.)
>  > 
>  > I don't recall objecting.  My only request is that the values
>  > selected be available with some switch somehow.
>  > r~
> 
> Not you, it's Richard Earnshaw. :-)
> 
> Richard Earnshaw wants me to put the heuristics in gcc.c and pass it
> to cc1 (et al) via specs using -param commands.  This has the
> advantage in that bug reports with the output of gcc -v testcase.c
> will show the memory heuristics used also, in case that is relevant to
> triggering the bug.
> http://gcc.gnu.org/ml/gcc-patches/2003-02/msg01011.html
> 
> Geoff Keating thinks that adds too much complexity for no gain and
> want it to remain as posted in the original patch.
> http://gcc.gnu.org/ml/gcc-patches/2003-02/msg01112.html

To be clear, I also want the output of gcc -v testcase.c to show the
memory heuristics used, maybe using

  printf ("--param ggc-min-expand=%d --param ggc-min-heapsize=%d\n" ...);
	
I just don't want to involve the driver in computing them.

-- 
- Geoffrey Keating <geoffk@geoffk.org>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]