[Bug libgomp/25883] libgomp call pthread functions directly

2017-09-20 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25883 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libgomp/25883] libgomp call pthread functions directly

2006-02-02 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-02-02 23:42 --- I should note that the pthread calls are not from the config directories but instead from the toplevel. This is just wrong. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25883

[Bug libgomp/25883] libgomp call pthread functions directly

2006-01-24 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-01-24 12:14 --- Actually gthr-* is there so we don't duplicate a config/* for the target library. Your proposal is wrong as some targets like AIX actually have multilib on the threads. -- http://gcc.gnu.org/bugzilla/show_bug.c

[Bug libgomp/25883] libgomp call pthread functions directly

2006-01-24 Thread jakub at gcc dot gnu dot org
--- Comment #1 from jakub at gcc dot gnu dot org 2006-01-24 08:50 --- That's a bad idea. While in libstdc++, libgcc, libobjc and libgfortran we want to support thread safety only optionally, depending whether libpthread (or its system counterpart) is linked in or not, in libgomp thread