public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66470] [4.8/4.9/5/6 Regression] TLS ICE due to ix86_split_long_move Date: Wed, 10 Jun 2015 09:26:00 -0000 [thread overview] Message-ID: <bug-66470-4-PZSVyfEacX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66470-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66470 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Wed Jun 10 09:26:06 2015 New Revision: 224321 URL: https://gcc.gnu.org/viewcvs?rev=224321&root=gcc&view=rev Log: PR target/66470 * config/i386/i386.c (ix86_split_long_move): For collisions involving direct tls segment refs, move the UNSPEC_TP possibly wrapped in ZERO_EXTEND out of the address for lea, to each of the memory loads. * gcc.dg/tls/pr66470.c: New test. * gcc.target/i386/pr66470.c: New test. Added: branches/gcc-4_9-branch/gcc/testsuite/gcc.dg/tls/pr66470.c branches/gcc-4_9-branch/gcc/testsuite/gcc.target/i386/pr66470.c Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/config/i386/i386.c branches/gcc-4_9-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-06-10 9:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-09 9:08 [Bug target/66470] New: " jakub at gcc dot gnu.org 2015-06-09 9:09 ` [Bug target/66470] " mpolacek at gcc dot gnu.org 2015-06-09 9:12 ` rguenth at gcc dot gnu.org 2015-06-09 10:07 ` jakub at gcc dot gnu.org 2015-06-10 9:13 ` jakub at gcc dot gnu.org 2015-06-10 9:16 ` jakub at gcc dot gnu.org 2015-06-10 9:26 ` jakub at gcc dot gnu.org [this message] 2015-06-10 9:34 ` jakub at gcc dot gnu.org 2015-06-10 9:35 ` jakub 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-66470-4-PZSVyfEacX@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).