This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/24475] gcc.dg/tls/pr24428.c execution test and gcc.dg/tls/pr24428-2.c execution test fail on IA32
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Nov 2005 18:09:38 -0000
- Subject: [Bug target/24475] gcc.dg/tls/pr24428.c execution test and gcc.dg/tls/pr24428-2.c execution test fail on IA32
- References: <bug-24475-230@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from joseph at codesourcery dot com 2005-11-09 18:09 -------
Subject: Re: gcc.dg/tls/pr24428.c execution test and
gcc.dg/tls/pr24428-2.c execution test fail on IA32
On Wed, 9 Nov 2005, jakub at gcc dot gnu dot org wrote:
> Works just fine here. What glibc are you using?
> pr24428.c and pr24428-2.c are the only dg-do run tls tests, so perhaps
> your libc doesn't support TLS at all?
The tests changed from failing to working on my (CodeSourcery Automatic
Testing System) nightly builds when I switched them from running on an
i686-pc-linux-gnu system to running on an x86_64 system (with more recent
libc), bootstrapping with an i686-pc-linux-gnu cross-compiler and
configuring with --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu
--target=i686-pc-linux-gnu; that is, the same compiler version failed
under the pure 32-bit environment but passed when building as 32-bit under
a 64-bit kernel (with more recent libc), and this was the only change in
test results between the two environments apart from
gcc.misc-tests/linkage.c which tries to link with programs built with
"cc". Both environments have some form of glibc 2.3.2; it's quite
possible the older one doesn't support TLS.
If the state of "libc doesn't support TLS" can reliably be detected then
perhaps the test should be marked UNSUPPORTED in that case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24475