public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/44450]  New: gcc.dg/lto/20090210 fails with emutls
@ 2010-06-07 17:00 ro at gcc dot gnu dot org
  0 siblings, 0 replies; only message in thread
From: ro at gcc dot gnu dot org @ 2010-06-07 17:00 UTC (permalink / raw)
  To: gcc-bugs

I've recently compared testsuite results on Solaris 11/x86 with --enable-tls
(the default) and --disable-tls before going on to investigate TLS problems on
Solaris 8 and 9, especially given that emutls has been broken on mainline (and
the
4.5 branch) for quite some time.

In doing so, I noticed an LTO testcase that fails with --disable-tls, but
passes
without:

+FAIL: gcc.dg/lto/20090210 c_lto_20090210_0.o-c_lto_20090210_1.o link, -O0
-fwhopr
+UNRESOLVED: gcc.dg/lto/20090210 c_lto_20090210_0.o-c_lto_20090210_1.o execute
-O0 -fwhopr

ld: fatal: symbol `__emutls_v.value.1595.2037' is multiply-defined:



+FAIL: gcc.dg/lto/20090210 c_lto_20090210_0.o-c_lto_20090210_1.o link, -O2
-fwhopr
+UNRESOLVED: gcc.dg/lto/20090210 c_lto_20090210_0.o-c_lto_20090210_1.o execute
-O2 -fwhopr

  likewise, just -O2


-- 
           Summary: gcc.dg/lto/20090210 fails with emutls
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Keywords: link-failure
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ro at gcc dot gnu dot org
 GCC build triplet: i386-pc-solaris2.11
  GCC host triplet: i386-pc-solaris2.11
GCC target triplet: i386-pc-solaris2.11


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44450


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-06-07 17:00 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-06-07 17:00 [Bug middle-end/44450] New: gcc.dg/lto/20090210 fails with emutls ro at gcc dot gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).