public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49515] [4.7 Regression] gcc.dg/torture/tls/thr-init-2.c  -O2  -fpic  execution test failure
Date: Thu, 23 Jun 2011 15:39:00 -0000	[thread overview]
Message-ID: <bug-49515-4-M6jihFgyGr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49515-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Richard Henderson <rth at gcc dot gnu.org> 2011-06-23 15:39:19 UTC ---
(In reply to comment #0)
> Does !dtprello relocation need live $16 register? The relevant patterns in
> alpha.md do not model that dependancy.

No, DTPREL relocations are constants.  They are the offset to be added
to a TLSLDM base value.  You can see that happening both in the old and
new code sequences.

The code difference you show cannot be the real problem.  The register
allocator has made a poorer choice in 4.7, leading to an extra move,
but the code that you show is exactly equivalent.

Is linker relaxation messing with this code sequence, perhaps?


  parent reply	other threads:[~2011-06-23 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 11:20 [Bug target/49515] New: " ubizjak at gmail dot com
2011-06-23 11:56 ` [Bug target/49515] " rguenth at gcc dot gnu.org
2011-06-23 15:39 ` rth at gcc dot gnu.org [this message]
2011-06-24  7:42 ` ubizjak at gmail dot com
2011-06-24  7:56 ` ubizjak at gmail dot com
2011-06-24 10:02 ` ubizjak at gmail dot com

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-49515-4-M6jihFgyGr@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).