Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=1822
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #1279 is|0 |1
obsolete| |
------- Additional Comments From [EMAIL PROTECTED] 2005-04-06 15:15 -------
Created an attachment (id=2342)
--> (https://bugs.freedesktop.org/attachment.cgi?id=2342&action=view)
tls-support-4.patch
Updates tls-support-3.patch to work against current CVS.
I think that there are a couple issues that remain before this code can start
going into CVS.
1. The build. Should TLS builds go in $(LIB_DIR)/tls? The whole build process
breaks down if, for example, a distro wants to build TLS and non-TLS versions
of everything. Can we just punt on this issue for now?
2. LD_KERNEL_ASSUME=2.4.19 stuff. Will the voodoo that's currently in
src/mesa/x86/glapi_x86.S work "as is" for other archs? If so, we can just put
that in its own file and always link it in.
3. Run-time inlining of get_dispatch. The original code from Jakub would copy
the code from get_dispatch into each of the dispatch functions at run-time.
This means the dispatch stubs need to be in a wtext section. This balanced
between run-time performance and the number of relocs.
4. There are a few things in src/glx/x11 that could be TLS-ized (e.g., the
current GLX context, etc.). This can probably wait until after the first batch
goes into CVS.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
