public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sumbera at volny dot cz" <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: Mon, 23 Nov 2020 14:29:51 +0000 [thread overview] Message-ID: <bug-96607-4-jhiUJ7aXiY@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 --- Comment #7 from Petr Sumbera <sumbera at volny dot cz> --- Just to confirm that '-fno-delayed-branch' as workaround seems to work (at least based on provided test case). Probably better is to modify the code like this: --- gcc-10.2.0/gcc/config/sparc/sparc.c +++ gcc-10.2.0/gcc/config/sparc/sparc.c @@ -3963,6 +3963,8 @@ if ((TARGET_GNU_TLS && HAVE_GNU_LD) || !TARGET_TLS) return 1; + return 0; + pat = PATTERN (trial); /* We must reject tgd_add{32|64}, i.e. --- Of course proper fix is needed. Any suggestion to the condition (in code) below?
next prev parent reply other threads:[~2020-11-23 14:29 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 ` [Bug target/96607] " ro at gcc dot gnu.org 2020-08-14 12:39 ` 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 [this message] 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-jhiUJ7aXiY@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: linkBe 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).