public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp.gcc@gmail.com>
To: Richard Biener <rguenther@suse.de>
Cc: rdapp.gcc@gmail.com, gcc-patches <gcc-patches@gcc.gnu.org>,
	Tamar.Christina@arm.com
Subject: Re: [PATCH] match.pd: Use element_mode instead of TYPE_MODE.
Date: Tue, 27 Jun 2023 08:47:58 +0200	[thread overview]
Message-ID: <0ea59340-7946-51dc-a060-6f0fc1ccdda0@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2306270628210.4723@jbgna.fhfr.qr>

> Can you push the element_mode change separately please?

OK.

> I'd like to hear more reasoning of why target_supports_op_p is wanted
> here.  Doesn't target_supports_op_p return false if this is for example
> a soft-fp target?  So if at all, shouldn't the test only be carried
> out if the original operation was supported by the target?

Tamar and I discussed whether a target check is appropriate yesterday
already here and were torn.  How or where would we expect a non-supported
operation to be discarded, though?  In my case the expression is generated
during a ranger fold and survives until expand where we ICE.

Regards
 Robin


  reply	other threads:[~2023-06-27  6:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 14:26 Robin Dapp
2023-06-26 23:18 ` Jeff Law
2023-06-27  6:30 ` Richard Biener
2023-06-27  6:47   ` Robin Dapp [this message]
2023-06-27  7:03     ` Richard Biener
2023-06-27  7:42       ` Robin Dapp
2023-06-27  8:46         ` Richard Biener
2023-06-27  9:42           ` Robin Dapp
2023-06-27  9:50             ` Richard Biener
2023-06-27  9:55               ` Robin Dapp
2023-06-27 10:05                 ` Richard Biener
2023-06-27 15:55                   ` Robin Dapp
2023-06-27 23:05                     ` Andrew Pinski
2023-06-28  7:27                       ` 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=0ea59340-7946-51dc-a060-6f0fc1ccdda0@gmail.com \
    --to=rdapp.gcc@gmail.com \
    --cc=Tamar.Christina@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).