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 target/96607] GCC feeds SPARC/Solaris linker with unrecognized TLS sequences
Date: Fri, 14 Aug 2020 12:38:19 +0000	[thread overview]
Message-ID: <bug-96607-4-LEtPDn6irl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96607-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96607

Rainer Orth <ro at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebotcazou at gcc dot gnu.org,
                   |                            |ro at gcc dot gnu.org

--- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> ---
To add some background: I've been experiencing ca. 250 test failures in the
LLVM
testsuite when building for sparcv9-sun-solaris2.11.

As a workaround, I've posted

  [cmake] Don't build with -O3 -fPIC on Solaris/sparcv9
  https://reviews.llvm.org/D85630

based on the observation that the SEGVs vanish if LLVM is compiled with -O
-fPIC
only instead of the default -O3 -fPIC.

I've been using the following slightly reduced example (attached):

* tqt.cpp is reduced from LLVM's llvm/unittests/Support/TaskQueueTest.cpp.

* ThreadPool.cpp is LLVM 10.0.0 llvm/lib/Support/ThreadPool.cpp.

They can be compiled and linked with the included tqt.sh; however that relies
on
LLVM 10 bundled with Solaris 11.4 for LLVM headers, libLLVMSupport and
libLLVMDemangle.

I haven't tried to produce a further reduced example yet.

  reply	other threads:[~2020-08-14 12:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 20:52 [Bug target/96607] New: " vita.batrla at gmail dot com
2020-08-14 12:38 ` ro at gcc dot gnu.org [this message]
2020-08-14 12:39 ` [Bug target/96607] " ro at gcc dot gnu.org
2020-09-02  9:38 ` ebotcazou at gcc dot gnu.org
2020-09-02  9:38 ` ebotcazou at gcc dot gnu.org
2020-10-06 11:04 ` sumbera at volny dot cz
2020-10-06 11:26 ` ebotcazou at gcc dot gnu.org
2020-11-23 14:29 ` sumbera at volny dot cz
2020-11-23 14:35 ` ebotcazou at gcc dot gnu.org
2020-11-26 15:42 ` cvs-commit at gcc dot gnu.org
2020-11-28  9:26 ` cvs-commit at gcc dot gnu.org
2020-11-28  9:27 ` cvs-commit at gcc dot gnu.org
2020-11-28  9:28 ` ebotcazou at gcc dot gnu.org

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-96607-4-LEtPDn6irl@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).