public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redlizard at redlizard dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60817] New: gcc configure script misdetects TLS support on x86_64-pc-solaris* with gnu as Date: Fri, 11 Apr 2014 05:56:00 -0000 [thread overview] Message-ID: <bug-60817-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60817 Bug ID: 60817 Summary: gcc configure script misdetects TLS support on x86_64-pc-solaris* with gnu as Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: redlizard at redlizard dot nl Created attachment 32584 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32584&action=edit Proposed patch. When building gcc >= 4.7 on x86_64-pc-solaris2.11 --with-gnu-as, the gcc/configure script incorrectly decides that gnu as does not support real TLS, and so unnecessarily decides to activate emutls instead. The solaris-specific test checks this support by trying to assemble a piece of TLS-using assembly code, and it uses the same 32-bit code for this test both on 32-bit and 64-bit platforms. The solaris assembler will accept this, but gnu as fails on the 32 bit code when targeting x86_64-pc-solaris*, thus causing the detection to fail. Attached patch for 4.9 fixes the problem, and is trivially backported to 4.8 and 4.7.
next reply other threads:[~2014-04-11 5:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-11 5:56 redlizard at redlizard dot nl [this message] 2014-04-11 13:19 ` [Bug target/60817] " ro at CeBiTec dot Uni-Bielefeld.DE 2014-04-11 15:49 ` redlizard at redlizard dot nl 2014-04-15 11:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2014-04-15 15:22 ` ro at gcc dot gnu.org 2014-04-16 9:10 ` ro at gcc dot gnu.org 2014-04-16 9:11 ` ro 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-60817-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: 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).