public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: rep.dot.nop@gmail.com, gcc-patches@gcc.gnu.org,
	Dimitar Dimitrov <dimitar@dinux.eu>,
	Jeff Law <jlaw@ventanamicro.com>
Cc: Jivan Hakobyan <jivanhakobyan9@gmail.com>
Subject: Re: [RFA] New pass for sign/zero extension elimination
Date: Mon, 27 Nov 2023 09:14:49 -0700	[thread overview]
Message-ID: <d04134ad-dd90-47fc-93c1-7f656e400622@gmail.com> (raw)
In-Reply-To: <C092C248-CC1A-429A-AD27-E3D3A5E18430@gmail.com>



On 11/26/23 09:42, rep.dot.nop@gmail.com wrote:
> On 22 November 2023 23:23:41 CET, Jeff Law <jeffreyalaw@gmail.com> wrote:
>>
>>
>> On 11/20/23 11:56, Dimitar Dimitrov wrote:
>>> On Sun, Nov 19, 2023 at 05:47:56PM -0700, Jeff Law wrote:
>>> ...
> 
>>>> +      enum rtx_code xcode = GET_CODE (x);
>>>> +      if (xcode == SET)
>>>> +	{
>>>> +	  const_rtx dst = SET_DEST (x);
>>>> +	  rtx src = SET_SRC (x);
>>>> +	  const_rtx y;
>>>> +	  unsigned HOST_WIDE_INT bit = 0;
>>>> +
>>>> +	  /* The code of the RHS of a SET.  */
>>>> +	  enum rtx_code code = GET_CODE (src);
>>>> +
>>>> +	  /* ?!? How much of this should mirror SET handling, potentially
>>>> +	     being shared?   */
>>>> +	  if (SUBREG_BYTE (dst).is_constant () && SUBREG_P (dst))
>>>
>>> Shouldn't SUBREG_P be checked first like:
>>> 	  if (SUBREG_P (dst) && SUBREG_BYTE (dst).is_constant ())
>> Yes, absolutely. It'll be fixed in the next update.
>>
>> This also highlighted that I never added pru-elf to the configurations in my tester.  I remember thinking that it needed to be added, but obviously that mental TODO got lost.  I've just fixed that.
> 
> 
> And please drop the superfluous enum from rtx_code while at it?
Sure.
jeff

  reply	other threads:[~2023-11-27 16:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  0:47 Jeff Law
2023-11-20  1:22 ` Oleg Endo
2023-11-20  2:51   ` Jeff Law
2023-11-20  2:57     ` Oleg Endo
2023-11-20  2:23 ` Xi Ruoyao
2023-11-20  2:46   ` Jeff Law
2023-11-20  2:52   ` Jeff Law
2023-11-20  3:32     ` Xi Ruoyao
2023-11-20  3:48       ` Jeff Law
2023-11-20 18:26 ` Richard Sandiford
2023-11-22 17:59   ` Jeff Law
2023-11-27 20:15     ` Richard Sandiford
2023-11-20 18:56 ` Dimitar Dimitrov
2023-11-22 22:23   ` Jeff Law
2023-11-26 16:42     ` rep.dot.nop
2023-11-27 16:14       ` Jeff Law [this message]
2023-11-27 11:30 ` Andrew Stubbs
2023-11-27 16:16   ` Jeff Law
2023-12-01  1:08 ` Hans-Peter Nilsson
2023-12-01 15:09   ` Jeff Law
2023-12-01 16:17     ` Hans-Peter Nilsson
2023-11-27 17:36 Joern Rennecke
2023-11-27 17:57 ` Joern Rennecke
2023-11-27 20:03   ` Richard Sandiford
2023-11-27 20:18     ` Jeff Law
2023-11-28 13:36       ` Joern Rennecke
2023-11-28 14:09         ` Joern Rennecke
2023-11-30 17:33         ` Jeff Law
2023-11-28 13:13     ` Joern Rennecke
2023-11-28  5:50 ` Jeff Law
2023-11-27 18:19 Joern Rennecke
2023-11-28  5:51 ` Jeff Law
2023-11-29 17:37 Joern Rennecke
2023-11-29 19:13 ` Jivan Hakobyan
2023-11-30 15:37 ` Jeff Law

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=d04134ad-dd90-47fc-93c1-7f656e400622@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=dimitar@dinux.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jivanhakobyan9@gmail.com \
    --cc=jlaw@ventanamicro.com \
    --cc=rep.dot.nop@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).