public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, iant@google.com
Subject: Re: [PATCH][GCC 7] Remove broken path in extract_bit_field_1
Date: Mon, 04 Apr 2016 13:10:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1604041508400.13384@t29.fhfr.qr> (raw)
In-Reply-To: <20160404130617.GD19207@tucnak.redhat.com>

On Mon, 4 Apr 2016, Jakub Jelinek wrote:

> On Mon, Apr 04, 2016 at 02:56:51PM +0200, Richard Biener wrote:
> > The testcase gcc.target/i386/pr37870.c will already ICE with that
> > patch, so no additional testcase.
> 
> In theory you could validate_subreg first and use that code if validation
> went ok, otherwise go through memory.
> But I admit I don't have anything in particular in mind where it would
> trigger this code and the subreg would successfully validate.

Not sure if it would help as that has

  /* ??? Similarly, e.g. with (subreg:DF (reg:TI)).  Though 
store_bit_field
     is the culprit here, and not the backends.  */
  else if (osize >= UNITS_PER_WORD && isize >= osize)
    ;

and thus we'd return true anyway for (subreg:XF (reg:TI) 0)

Richard.

> > 2016-04-04  Richard Biener  <rguenther@suse.de>
> > 
> > 	PR middle-end/37870
> > 	* expmed.c (extract_bit_field_1): Remove broken case
> > 	using a wider MODE_INT mode.
> > 
> > Index: gcc/expmed.c
> > ===================================================================
> > --- gcc/expmed.c	(revision 234708)
> > +++ gcc/expmed.c	(working copy)
> > @@ -1647,17 +1647,6 @@ extract_bit_field_1 (rtx str_rtx, unsign
> >  	    if (GET_CODE (op0) == SUBREG)
> >  	      op0 = force_reg (imode, op0);
> >  	  }
> > -	else if (REG_P (op0))
> > -	  {
> > -	    rtx reg, subreg;
> > -	    imode = smallest_mode_for_size (GET_MODE_BITSIZE (GET_MODE (op0)),
> > -					    MODE_INT);
> > -	    reg = gen_reg_rtx (imode);
> > -	    subreg = gen_lowpart_SUBREG (GET_MODE (op0), reg);
> > -	    emit_move_insn (subreg, op0);
> > -	    op0 = reg;
> > -	    bitnum += SUBREG_BYTE (subreg) * BITS_PER_UNIT;
> > -	  }
> >  	else
> >  	  {
> >  	    HOST_WIDE_INT size = GET_MODE_SIZE (GET_MODE (op0));
> 
> 	Jakub
> 
> 

-- 
Richard Biener <rguenther@suse.de>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

  reply	other threads:[~2016-04-04 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 12:57 Richard Biener
2016-04-04 13:06 ` Jakub Jelinek
2016-04-04 13:10   ` Richard Biener [this message]
2016-04-04 13:24     ` Jakub Jelinek
2016-04-04 13:27       ` Richard Biener
2016-04-04 13:33         ` Jakub Jelinek
2016-04-18  9:26           ` Richard Biener

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=alpine.LSU.2.11.1604041508400.13384@t29.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=jakub@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).