This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Reason for cygwin GCC 2.97 non-bootstrap found
- To: Zack Weinberg <zackw at Stanford dot EDU>
- Subject: Re: Reason for cygwin GCC 2.97 non-bootstrap found
- From: Richard Henderson <rth at redhat dot com>
- Date: Mon, 20 Nov 2000 19:24:14 -0800
- Cc: Kelley Cook <Kelley dot Cook at home dot com>, Cygwin mailing list <Cygwin at sources dot redhat dot com>, GCC Bugs <gcc-bugs at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- References: <200011202245.eAKMjjN27680@plmlir3.mail.eds.com> <20001120154222.O17712@wolery.stanford.edu>
On Mon, Nov 20, 2000 at 03:42:23PM -0800, Zack Weinberg wrote:
> +#if use_malloc
> + return (char *) malloc (size);
> +#endif
[...]
> + return res + offset;
I refuse to believe that there exists any magic size/roundup/offset
combination that *always* returns a full page of aligned memory.
The only semi-decent solution I can think of is to get N*pagesize+C
bytes from malloc, which can then be delivered as N' aligned data pages,
plus a control block of size C to determine when the entire block may
be freed. N' will normally be N-1, but could accidentally be N.
Moreover, I think the ggc-page mmap optimizations are useful enough
that I do not want to defer everything to an xvalloc or the like.
r~
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com