public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joern Rennecke" <joernr@arc.com>
To: "Uros Bizjak" <ubizjak@gmail.com>
Cc: "GCC Development" <gcc@gcc.gnu.org>
Subject: Re: Invalid reload inheritance with paradoxical subregs
Date: Thu, 02 Apr 2009 14:58:00 -0000	[thread overview]
Message-ID: <20090402145758.GF26057@elsdt-razorfish.arc.com> (raw)
In-Reply-To: <5787cf470904020351ve8a375bq455a31c185443f82@mail.gmail.com>

On Thu, Apr 02, 2009 at 12:51:55PM +0200, Uros Bizjak wrote:
> I guess that somehow we have to prevent choose_reload_regs to blindly
> substitute memory_operand with register when paradoxical subregs are
> involved. The condition for the substitution should be similar to the
> condition in nonzero_bits1 from final.c:


Yes.  It would be nicer if we could get rid of these special meanings
of paradoxical subregs and instead used ZERO_EXTEND and SIGN_EXTEND in
their place; this would also give better code for target that can
have either of these.  However, that would not only require changes to
reload to reload these properly, but also to all the affected targets,
e.g. rtx_costs would have to discount the cost of the extension operation. 
This e-mail was sent from a group e-mail system of ARC International Plc. Full details of the registered names and addresses of companies within the ARC group can be found on the ARC website.ARC International plc, Registered Office: Verulam Point, Station WaySt. Albans AL1 5HE United Kingdom Registered in England and Wales No.  3592130savm-exch03 
 
 
 
 
 
 
 

  reply	other threads:[~2009-04-02 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 13:35 Joern Rennecke
2009-04-02 10:52 ` Uros Bizjak
2009-04-02 14:58   ` Joern Rennecke [this message]
2009-04-06 16:28   ` Hans-Peter Nilsson
2009-04-06 18:28     ` Uros Bizjak
2009-04-06 19:06       ` Hans-Peter Nilsson
  -- strict thread matches above, loose matches on Subject: below --
2009-04-01 13:15 Uros Bizjak

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=20090402145758.GF26057@elsdt-razorfish.arc.com \
    --to=joernr@arc.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ubizjak@gmail.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).