[patch][google/integration] Don't force tls-model to initial-exec when building libgomp (issue6107046)

2012-04-22 Thread Paul Pluzhnikov
Greetings, The patch below is needed for google/integration branch: we want to be able build libgomp.a with -fPIC, be able to link it into a shared library, and be able to dlopen that library without running out of static TLS space (-ftls-model=initial-exec precludes that last part). Google ref

Re: [patch][google/integration] Don't force tls-model to initial-exec when building libgomp (issue6107046)

2012-04-22 Thread Andrew Pinski
On Sun, Apr 22, 2012 at 10:50 AM, Paul Pluzhnikov ppluzhni...@google.com wrote: Greetings, The patch below is needed for google/integration branch: we want to be able build libgomp.a with -fPIC, be able to link it into a shared library, and be able to dlopen that library without running out

Re: [patch][google/integration] Don't force tls-model to initial-exec when building libgomp (issue6107046)

2012-04-22 Thread Jakub Jelinek
On Sun, Apr 22, 2012 at 10:09:46PM -0700, Andrew Pinski wrote: On Sun, Apr 22, 2012 at 10:50 AM, Paul Pluzhnikov ppluzhni...@google.com wrote: Greetings, The patch below is needed for google/integration branch: we want to be able build libgomp.a with -fPIC, be able to link it into a

Re: [patch][google/integration] Don't force tls-model to initial-exec when building libgomp (issue6107046)

2012-04-22 Thread Paul Pluzhnikov
On Sun, Apr 22, 2012 at 10:09 PM, Andrew Pinski pins...@gmail.com wrote: IIRC the main reason is because the slow down from not using initial-exec model for GOMP is a lot. Given a choice between slows down a lot and doesn't work at all, we prefer the former ;-) I see that we are not alone: