public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/50654] New: Many Go tests fail on emutls targets
Date: Fri, 07 Oct 2011 09:25:00 -0000	[thread overview]
Message-ID: <bug-50654-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50654
           Summary: Many Go tests fail on emutls targets
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
        AssignedTo: ian@airs.com
        ReportedBy: ro@gcc.gnu.org
              Host: *-*-solaris2.[89]
            Target: *-*-solaris2.[89]
             Build: *-*-solaris2.[89]


Between 20110930 and 20111006, many Go tests started to FAIL on Solaris 8 and
9/x86 (haven't tried SPARC yet) with Sun as, thus they use emutls:

output is:
Undefined            first referenced

 symbol                  in file

__emutls_v.__go_panic_defer        
/var/gcc/regression/trunk/8-gcc/build/i386-pc-solaris2.8/./libgo/.libs/libgo.so

__emutls_v.m                       
/var/gcc/regression/trunk/8-gcc/build/i386-pc-solaris2.8/./libgo/.libs/libgo.so

ld: fatal: Symbol referencing errors. No output written to
/var/gcc/regression/trunk/8-gcc/build/gcc/testsuite/go/array-1.x

collect2: error: ld returned 1 exit status


FAIL: go.go-torture/execute/array-1.go compilation,  -O0 

With gas and native TLS, the tests work fine.

  Rainer


             reply	other threads:[~2011-10-07  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  9:25 ro at gcc dot gnu.org [this message]
2011-10-07  9:27 ` [Bug go/50654] " ro at gcc dot gnu.org
2012-02-14  0:38 ` ian at gcc dot gnu.org
2012-02-14  0:41 ` ian at airs dot com
2012-02-16 19:50 ` ro at CeBiTec dot Uni-Bielefeld.DE

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-50654-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).