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 [EMAIL PROTECTED]
- Reason for cygwin GCC 2.97 non-bootstrap found Kelley Cook
- Re: Reason for cygwin GCC 2.97 non-bootstrap found DJ Delorie
- Re: Reason for cygwin GCC 2.97 non-bootstrap found Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-bootstrap f... Christopher Faylor
- Re: Reason for cygwin GCC 2.97 non-bootstr... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-boo... Christopher Faylor
- Re: Reason for cygwin GCC 2.97 no... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-bootstrap f... Richard Henderson
- Re: Reason for cygwin GCC 2.97 non-bootstr... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-boo... Richard Henderson
- Re: Reason for cygwin GCC 2.97 no... DJ Delorie
- Re: Reason for cygwin GCC 2.9... Richard Henderson
- Re: Reason for cygwin GCC... DJ Delorie
- Re: Reason for cygwin GCC 2.97 non-bootstrap found Kelley Cook
- Re: Reason for cygwin GCC 2.97 non-bootstrap f... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 non-bootstr... Phil Edwards
- Re: Reason for cygwin GCC 2.97 non-boo... Zack Weinberg
- Re: Reason for cygwin GCC 2.97 no... Chris Abbey
