This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descrstructure
- From: "David S. Miller" <davem at redhat dot com>
- To: gareth dot hughes at acm dot org
- Cc: drepper at redhat dot com, libc-alpha at sources dot redhat dot com, dri-devel at lists dot sourceforge dot net
- Date: Tue, 21 May 2002 14:46:01 -0700 (PDT)
- Subject: Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descrstructure
- References: <3CE47412.408@acm.org><1021878152.30693.2.camel@myware.mynet><3CEAB6C1.1080906@acm.org>
From: Gareth Hughes <gareth.hughes@acm.org>
Date: Tue, 21 May 2002 14:06:09 -0700
In the mean time, a few questions:
- Does __thread require -fPIC? From my initial reading of the PDF
document on your website, I was under the impression that this was
the case.
Why does it matter? Jakub has shown how to get the same kind of
non-PIC relocations you want in the GL libraries by using private
versions of symbols.
Also, the PIC register argument is bogus too. I know for a fact that
current GCC will fully allow allocation of the x86 PIC register
if you make no references to PIC relocatable data. %99 of functions
in an OpenGL implementation will get full use of the PIC register,
_ESPECIALLY_ if you use the privatization symbol tricks Jakub
mentioned.
It should be rare to reference PIC symbols from within OpenGL if done
properly, thus the PIC register and the relocation arguments are null
and void.
Franks a lot,
David S. Miller
davem@redhat.com