public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: Richard Henderson <rth@cygnus.com>
Cc: egcs@cygnus.com, gcc2@cygnus.com
Subject: Re: double_reg_address_ok
Date: Wed, 08 Apr 1998 02:13:00 -0000	[thread overview]
Message-ID: <199804072152.OAA26002@rtl.cygnus.com> (raw)
In-Reply-To: <19980405034830.11235@dot.cygnus.com>

	There does not currently appear to be anything about the code that
	is predicated on double_reg_address_ok that seems to require that
	the result be offsettable.

There are places in reload where it assumes that if an address has been
reloaded already, then it must be offsettable.  This avoids needing multiple
possibly conflicting reloads for the same address.  See the 'o' case in
reload.c.

See in particular the reg_equiv_address case.  If we have an address using
an unallocated pseudo, and that pseudo lives in a stack slot with such a
large offset that it can't be accessed with a REG+CONST_INT addressing mode,
and we need this address to be offsettable, then using a REG+REG addressing
mode to access it will fail.  Hence we can't allow reload to generate it.
This is just an educated guess though, so I am not sure if it is right.
And if it is right, there may be an easy way to work around it but that no
one has tried yet.

Jim

      parent reply	other threads:[~1998-04-08  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-05  5:39 double_reg_address_ok Richard Henderson
1998-04-05 17:27 ` double_reg_address_ok Richard Henderson
1998-04-06 17:35 ` double_reg_address_ok Jeffrey A Law
1998-04-08  2:13 ` Jim Wilson [this message]

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=199804072152.OAA26002@rtl.cygnus.com \
    --to=wilson@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=gcc2@cygnus.com \
    --cc=rth@cygnus.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).