delorie.com/archives/browse.cgi | search |
Date: | Sat, 06 Jan 2001 13:45:12 +0200 |
From: | "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> |
Sender: | halo1 AT zahav DOT net DOT il |
To: | "Mark E." <snowball3 AT bigfoot DOT com> |
Message-Id: | <3028-Sat06Jan2001134512+0200-eliz@is.elta.co.il> |
X-Mailer: | Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 |
CC: | djgpp-workers AT delorie DOT com |
In-reply-to: | <3A55C132.12287.6F26E9@localhost> (snowball3@bigfoot.com) |
Subject: | Re: valloc and memalign draft |
References: | <3A55C132 DOT 12287 DOT 6F26E9 AT localhost> |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> From: "Mark E." <snowball3 AT bigfoot DOT com> > Date: Fri, 5 Jan 2001 12:42:26 -0500 > > This is a draft of valloc (and memalign) designed to used mainly by the GCC's > garbage collection routines. I designed it to be memory efficient and return > a pointer that can safely be passed to free(). While a generic valloc is in > the works for inclusion in libiberty, it's always better to have our own > version if possible. Shouldn't align_val and split_alloc be declared static?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |