public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Tamar Christina <Tamar.Christina@arm.com>,
	Richard Biener <rguenther@suse.de>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	nd <nd@arm.com>,
	richard.sandiford@arm.com
Subject: Re: [PATCH 1/2]middle-end: RFC: On expansion of conditional branches, give hint if argument is a truth type to backend
Date: Thu, 29 Sep 2022 14:49:06 -0600	[thread overview]
Message-ID: <69338309-8c9b-c93c-1df3-24e10b9452c4@gmail.com> (raw)
In-Reply-To: <mpt7d1mv7w5.fsf@arm.com>


On 9/29/22 03:37, Richard Sandiford wrote:
> Jeff Law <jeffreyalaw@gmail.com> writes:
>> On 9/28/22 09:04, Richard Sandiford wrote:
>>> Tamar Christina <Tamar.Christina@arm.com> writes:
>>>>> Maybe the target could use (subreg:SI (reg:BI ...)) as argument. Heh.
>>>> But then I'd still need to change the expansion code. I suppose this could
>>>> prevent the issue with changes to code on other targets.
>>>>
>>>>>>> We have undocumented addcc, negcc, etc. patterns, should we have aandcc
>>>> pattern for this indicating support for andcc + jump as opposedto cmpcc + jump?
>>>>>> This could work yeah. I didn't know these existed.
>>>>> Ah, so they are conditional add, not add setting CC, so andcc wouldn't
>>>>> be appropriate.
>>>>> So I'm not sure how we'd handle such situation - maybe looking at
>>>>> REG_DECL and recognizing a _Bool PARM_DECL is OK?
>>>> I have a slight suspicion that Richard Sandiford would likely reject this
>>>> though..
>>> Good guess :-P  We shouldn't rely on something like that for correctness.
>>>
>>> Would it help if we promoted the test-and-branch instructions to optabs,
>>> alongside cbranch?  The jump expanders could then target it directly.
>>>
>>> IMO that'd be a reasonable thing to do if it does help.  It's a relatively
>>> common operation, especially on CISCy targets.
>> But don't we represent these single bit tests using zero_extract as the
>> condition of the branch?  I guess if we can generate them directly
>> rather than waiting for combine to deduce that we're dealing with a
>> single bit test and constructing the zero_extract form would be an
>> improvement and might help aarch at the same time.
> Do you mean that the promote_mode stuff should use ext(z)v rather than
> zero_extend to promote a bool, where available?

No, just that if we're doing a single bit test that the way to handle 
that is with a zero_extract and the earlier we can generate that form, 
the better.


Jeff


  parent reply	other threads:[~2022-09-29 20:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  9:24 Tamar Christina
2022-09-23  9:25 ` [PATCH 2/2]AArch64 Extend tbz pattern to allow SI to SI extensions Tamar Christina
2022-09-23  9:42   ` Richard Sandiford
2022-09-23  9:48     ` Tamar Christina
2022-09-26 10:35 ` [PATCH 1/2]middle-end: RFC: On expansion of conditional branches, give hint if argument is a truth type to backend Richard Biener
2022-09-26 11:05   ` Tamar Christina
2022-09-26 11:32     ` Richard Biener
2022-09-26 11:46       ` Tamar Christina
2022-09-26 12:34         ` Richard Biener
2022-09-26 12:43           ` Richard Biener
2022-09-26 14:02             ` Tamar Christina
2022-09-28 15:04         ` Richard Sandiford
2022-09-28 17:23           ` Jeff Law
2022-09-29  9:37             ` Richard Sandiford
2022-09-29  9:40               ` Richard Biener
2022-09-29 10:21                 ` Tamar Christina
2022-09-29 11:09                   ` Richard Biener
2022-09-30  8:00                     ` Tamar Christina
2022-09-30  8:28                       ` Richard Sandiford
2022-09-30  8:38                         ` Tamar Christina
2022-09-30  8:48                           ` Richard Sandiford
2022-09-30  9:15                             ` Tamar Christina
2022-09-30 10:16                               ` Richard Biener
2022-09-30 11:11                                 ` Tamar Christina
2022-09-30 11:52                                   ` Richard Biener
2022-09-30 12:48                                     ` Tamar Christina
2022-09-30 14:28                                       ` Richard Sandiford
2022-09-30 14:33                                         ` Richard Biener
2022-09-29 20:49               ` Jeff Law [this message]
2022-10-27  3:22 ` Andrew Pinski

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=69338309-8c9b-c93c-1df3-24e10b9452c4@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=Tamar.Christina@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.com \
    --cc=rguenther@suse.de \
    --cc=richard.sandiford@arm.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).