This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/35677] Intermitent failure "FAIL: libgomp.fortran/crayptr2.f90"
- From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Dec 2008 19:27:47 -0000
- Subject: [Bug testsuite/35677] Intermitent failure "FAIL: libgomp.fortran/crayptr2.f90"
- References: <bug-35677-12313@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #22 from dave at hiauly1 dot hia dot nrc dot ca 2008-12-12 19:27 -------
Subject: Re: Intermitent failure "FAIL: libgomp.fortran/crayptr2.f90"
> My long term guidance would be to engineer gcc to use its copy of the libgcc_s
> dylib and link against it. This would mean that the newly installed libgcc_s
> should be found first, over /usr/lib, and that development and support mirror
> linux, in all the usual ways.
That's certainly reasonable. However, linux style TLS support needs
help from the assembler, linker and dynamic loader. So, unless this
is going to happen, the best that can be achieved is that provided by
the emulation layer.
Tracking linux might be straight forward if the kernel supported ELF
executables. Then, x86 linux tools would work essentially as is.
However, I'm sure there would be issues with syscalls, etc.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35677