The use of the XFree routines are guarded like this:
#if defined(XFree86LOADER) && defined(IN_MODULE)
xf86free(ptr);
#else
free(ptr);
#endif
Does XFree86LOADER and IN_MODULE impact DRI objects or is it ok to use
libc ones?
Now that DRI is building in the mesa tree it should be possible to
remove all references to the X server. Does anyone know of an exception
to this?
--- Keith Packard <[EMAIL PROTECTED]> wrote:
>
> Around 10 o'clock on Jul 17, Jon Smirl wrote:
>
> > Can we switch DRI/mesa to use the standard malloc/free and forget
> about
> > the one in the X server? If not we will need some kind of run-time
> fix up.
>
> Seems like DRI/mesa should just use malloc/free for objects which
> aren't
> related to the X server internals. I've given up building custom
> allocators these days; the libc ones are almost always better
> designed for
> 'unusual' events (cf the XFree86 4.0 custom allocator which produced
> some
> spectactular results for large region computations).
>
> -keith
>
>
>
> ATTACHMENT part 2 application/pgp-signature
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
