public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54445] TLS array lookup with negative constant is not combined into a single instruction
Date: Sun, 02 Sep 2012 14:06:00 -0000	[thread overview]
Message-ID: <bug-54445-4-OfgJSewC0F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54445-4@http.gcc.gnu.org/bugzilla/>

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at redhat dot com

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> 2012-09-02 14:06:26 UTC ---
(In reply to comment #2)
> This is due to the definition of x86_64_immediate_operand predicate, following
> part:
> 
>         case UNSPEC:
>           switch (XINT (op1, 1))
>         {
>         case UNSPEC_DTPOFF:
>         case UNSPEC_NTPOFF:
>           if (offset > 0
>               && trunc_int_for_mode (offset, SImode) == offset)
>             return true;
>         }
> 
> I don't know why negative offsets are not allowed here.

It was added by

http://gcc.gnu.org/ml/gcc-cvs/2002-10/msg00685.html
http://gcc.gnu.org/git/?p=gcc.git;a=commit;h=29d8dd5cee1f9ebd56b4473a690fcc54ad986265


  parent reply	other threads:[~2012-09-02 14:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-01  0:40 [Bug target/54445] New: " adam at consulting dot net.nz
2012-09-01  3:00 ` [Bug target/54445] " adam at consulting dot net.nz
2012-09-01 14:54 ` ubizjak at gmail dot com
2012-09-01 16:59 ` hjl.tools at gmail dot com
2012-09-02 14:06 ` hjl.tools at gmail dot com [this message]
2012-09-02 14:21 ` hjl.tools at gmail dot com
2012-09-12 18:09 ` hjl at gcc dot gnu.org
2012-09-12 18:10 ` hjl.tools at gmail dot com
2012-09-12 18:11 ` hjl at gcc dot gnu.org
2012-09-13  9:02 ` adam at consulting dot net.nz

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-54445-4-OfgJSewC0F@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).