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
> Ok if it'll help move things forward. Whom shall I ask?
> assign@gnu.org? Or do you want to do it?
That's probably a good address to use. Or legal@gnu.org (although
they're probably the same person). I suspect it will be ok, but I'm
paranoid.
> I.e. in my efforts related to GCC
Ah, but it's going into libiberty because you forsee it being useful
to non-gcc projects. libstdc++ often invokes these types of problems,
for example, because it is GPL plus exceptions. Will libstdc++ ever
have a memory-defined optimization?
> > I'd prefer a "long long" type (say, int64_t or something) if there was
> > some way to get it in there portably. Given that it's a header, we
> > can't always rely on autoconf providing the checks we need. Double
> > would at least be guaranteed to work properly in all cases.
>
> Agreed. So we're going to keep it as-is then, right?
Yeah, let's keep it double. The autoconf headaches exceed the FPU
headaches.