This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: Paul Pluzhnikov <ppluzhnikov at google dot com>
To: Andrew Pinski <pinskia at gmail dot com>
Cc: reply at codereview dot appspotmail dot com, gcc-patches at gcc dot gnu dot org
Date: Sun, 22 Apr 2012 22:31:54 -0700
Subject: Re: [patch][google/integration] Don't force tls-model to initial-exec when building libgomp (issue6107046)
References: <20120422175040.224BE190A4E@elbrus2.mtv.corp.google.com> <CA+=Sn1mjH2nYD9juc8pypssWZaz0HD0y5cbxro5O6EFmq5d8rA@mail.gmail.com>

On Sun, Apr 22, 2012 at 10:09 PM, Andrew Pinski <pinskia@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:
http://old.nabble.com/-patch--libgomp%3A-removing-nodlopen-flag-for-portability-td10286039.html

Generally we don't use OpenMP, but some of our third-party libraries
do depend on it.

Thanks for the heads-up.
-- 
Paul Pluzhnikov

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

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]