public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: gcc-patches@gcc.gnu.org
Subject: ping^3 [PATCH] Subreg handling in reload_inner_reg_of_subreg() and 	push_reload()
Date: Thu, 30 Aug 2007 08:50:00 -0000	[thread overview]
Message-ID: <20070830082832.GE25795@sygehus.dk> (raw)
In-Reply-To: <20070730161023.GO25795@sygehus.dk>

On Mon, Jul 30, 2007 at 06:10:23PM +0200, Rask Ingemann Lambertsen wrote:
>    In <URL:http://gcc.gnu.org/ml/gcc/2007-05/msg00505.html> and
> <URL:http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01570.html> (which was
> briefly discussed) I described a case where reload is given HImode subreg of
> a multiword SImode hard reg. Because the HImode subreg is made of two QImode
> hard regs rather than one HImode hard reg, reload decides to write to the
> whole SImode hard reg instead of just the HImode subreg on the assumption
> that the subreg is "problematic", as a comment puts it. In fact, the rest of
> reload handles such a subreg just fine with no special treatment. This patch
> adjusts the checks in reload_inner_reg_of_subreg() and push_reload()
> accordingly.
> 
>    This and the other two reload patches in this patch set were bootstrapped
> and tested together on x86_64-unknown-linux-gnu with no new failures. I also
> built and tested cross compilers for arm-unknown-elf, cris-axis-elf,
> m32c-unknown-elf, mipsisa64-unknown-elf, sh-unknown-elf and v850-unknown-elf
> with no new failures.
> 
>    Ok for trunk?
> 
> 2007-07-30  Rask Ingemann Lambertsen  <rask@sygehus.dk>
> 
> 	* reload.c (reload_inner_reg_of_subreg): No special handling is
> 	  needed if a subreg consists of more hard regs than words.
> 	  (push_reload): Likewise.
> 
> Index: gcc/reload.c
> ===================================================================
> --- gcc/reload.c	(revision 126653)
> +++ gcc/reload.c	(working copy)
> @@ -809,13 +809,13 @@ reload_inner_reg_of_subreg (rtx x, enum 
>      return 1;
>  
>    /* If the outer part is a word or smaller, INNER larger than a
> -     word and the number of regs for INNER is not the same as the
> +     word and the number of regs for INNER is smaller than the
>       number of words in INNER, then INNER will need reloading.  */
>    return (GET_MODE_SIZE (mode) <= UNITS_PER_WORD
>  	  && output
>  	  && GET_MODE_SIZE (GET_MODE (inner)) > UNITS_PER_WORD
>  	  && ((GET_MODE_SIZE (GET_MODE (inner)) / UNITS_PER_WORD)
> -	      != (int) hard_regno_nregs[REGNO (inner)][GET_MODE (inner)]));
> +	      > (int) hard_regno_nregs[REGNO (inner)][GET_MODE (inner)]));
>  }
>  
>  /* Return nonzero if IN can be reloaded into REGNO with mode MODE without
> @@ -1035,8 +1035,8 @@ push_reload (rtx in, rtx out, rtx *inloc
>  		       > UNITS_PER_WORD)
>  		   && ((GET_MODE_SIZE (GET_MODE (SUBREG_REG (in)))
>  			/ UNITS_PER_WORD)
> -		       != (int) hard_regno_nregs[REGNO (SUBREG_REG (in))]
> -						[GET_MODE (SUBREG_REG (in))]))
> +		       > (int) hard_regno_nregs[REGNO (SUBREG_REG (in))]
> +					       [GET_MODE (SUBREG_REG (in))]))
>  		  || ! HARD_REGNO_MODE_OK (subreg_regno (in), inmode)))
>  	  || (secondary_reload_class (1, class, inmode, in) != NO_REGS
>  	      && (secondary_reload_class (1, class, GET_MODE (SUBREG_REG (in)),
> @@ -1128,8 +1128,8 @@ push_reload (rtx in, rtx out, rtx *inloc
>  		       > UNITS_PER_WORD)
>  		   && ((GET_MODE_SIZE (GET_MODE (SUBREG_REG (out)))
>  			/ UNITS_PER_WORD)
> -		       != (int) hard_regno_nregs[REGNO (SUBREG_REG (out))]
> -						[GET_MODE (SUBREG_REG (out))]))
> +		       > (int) hard_regno_nregs[REGNO (SUBREG_REG (out))]
> +					       [GET_MODE (SUBREG_REG (out))]))
>  		  || ! HARD_REGNO_MODE_OK (subreg_regno (out), outmode)))
>  	  || (secondary_reload_class (0, class, outmode, out) != NO_REGS
>  	      && (secondary_reload_class (0, class, GET_MODE (SUBREG_REG (out)),
> 
> -- 
> Rask Ingemann Lambertsen

  parent reply	other threads:[~2007-08-30  8:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 14:37 [PATCH 0/9] New back end ia16: 16-bit Intel x86 Rask Ingemann Lambertsen
2007-07-30 14:56 ` [PATCH 1/9] New target " Rask Ingemann Lambertsen
2007-07-30 15:08 ` [PATCH 2/9] Fix reloads_unique_chain_p() missing a conflict Rask Ingemann Lambertsen
2007-08-10  8:47   ` PING " Rask Ingemann Lambertsen
2007-08-21 11:23   ` ping^2 " Rask Ingemann Lambertsen
2007-08-30  8:28   ` ping^3 [PATCH] " Rask Ingemann Lambertsen
2007-07-30 16:10 ` [PATCH 3/9] reload_reg_free(): Rask Ingemann Lambertsen
2007-08-10  8:49   ` PING [PATCH 3/9] reload_reg_free(): don't clobber inherited registers Rask Ingemann Lambertsen
2007-08-21 11:24   ` ping^2 " Rask Ingemann Lambertsen
2007-08-30  8:50   ` ping^3 [PATCH] " Rask Ingemann Lambertsen
2007-07-30 16:35 ` [PATCH 4/9] Subreg handling in reload_inner_reg_of_subreg() and push_reload() Rask Ingemann Lambertsen
2007-08-10  8:49   ` PING " Rask Ingemann Lambertsen
2007-08-21 11:29   ` ping^2 " Rask Ingemann Lambertsen
2007-08-30  8:50   ` Rask Ingemann Lambertsen [this message]
2007-07-30 17:22 ` [PATCH 5/9] Libgcc bits and the back end itself Rask Ingemann Lambertsen
2007-07-30 19:08 ` [PATCH 6/9] Documentation for the ia16 back end Rask Ingemann Lambertsen
2007-08-11 19:01   ` Joseph S. Myers
2007-07-30 19:10 ` [PATCH 7/9][wwwdocs] Mention ia16 in backends.html Rask Ingemann Lambertsen
2007-07-30 22:48   ` Gerald Pfeifer
2007-07-30 19:36 ` [PATCH 8/9] Vectorizer testsuite fixes Rask Ingemann Lambertsen
2007-07-30 20:40   ` Janis Johnson
2007-07-30 20:08 ` [PATCH 9/9] Skip or xfail some tests on ia16 Rask Ingemann Lambertsen
2007-07-30 20:51   ` Janis Johnson
2007-08-09 20:28 ` [PATCH 0/9] New back end ia16: 16-bit Intel x86 Rask Ingemann Lambertsen

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=20070830082832.GE25795@sygehus.dk \
    --to=rask@sygehus.dk \
    --cc=gcc-patches@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).