public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jan Hubicka <jh@suse.cz>, gcc-patches@gcc.gnu.org, rth@redhat.com
Subject: Re: Fix x86-64 PIC
Date: Tue, 29 Oct 2002 12:55:00 -0000	[thread overview]
Message-ID: <20021029205512.GM23564@kam.mff.cuni.cz> (raw)
In-Reply-To: <20021029154708.H10988@devserv.devel.redhat.com>

> On Tue, Oct 29, 2002 at 09:41:07PM +0100, Jan Hubicka wrote:
> > > Could you please post some testcases of source lousy code?
> > > I'd like to know what valid 32-bit sign extended values my recent x86_64_sign_extended_value
> > > changes don't catch.
> > 
> > static int t;
> > q()
> > {
> >   t=1;
> > }
> > &t is not sign_extended_value, but t(%rip) is valid and recognized by the
> > pic_operand later.
> 
> With -O2 -fpic I get:
> q:
> 	movl    $1, t(%rip)
>         ret
> t is a x86_64_sign_extended_value in CM_SMALL_PIC model (since 2002-10-21).
OK,
I now see what you did.  I had old checkout that had this broken.
I don't think it makes sense to add allowrip for
x86_64_sign_extended_value and I think you are wrong to allow it in
x86_64_general_operand and friends since these can not be RIP relative
except for addresses that goes trought valid_address code anyway.  What
did you needed?

Honza

  parent reply	other threads:[~2002-10-29 20:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 11:23 Jan Hubicka
2002-10-29 12:39 ` Jakub Jelinek
2002-10-29 12:41   ` Jan Hubicka
2002-10-29 12:47     ` Jakub Jelinek
2002-10-29 12:48       ` Jan Hubicka
2002-10-29 12:55       ` Jan Hubicka [this message]
2002-10-29 12:48     ` Jan Hubicka
2002-10-29 12:55       ` Jakub Jelinek
2002-10-29 13:04         ` Jan Hubicka
2002-10-29 14:46         ` Jan Hubicka

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=20021029205512.GM23564@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rth@redhat.com \
    /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).