public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>,
	gcc-patches@gcc.gnu.org,        richard.sandiford@arm.com
Subject: Re: [PATCH] Fix vector rsqrt discovery (PR tree-optimization/68501)
Date: Mon, 30 Nov 2015 14:43:00 -0000	[thread overview]
Message-ID: <20151130143644.GE5675@tucnak.redhat.com> (raw)
In-Reply-To: <87a8pvef0z.fsf@e105548-lin.cambridge.arm.com>

On Mon, Nov 30, 2015 at 02:30:04PM +0000, Richard Sandiford wrote:
> > keep the builtin_reciprocal hook (perhaps renamed to builtin_rsqrt)
> > for the purpose of this condition and nothing else (i.e. return a
> > boolean) and let the rest be determined from the optab, just commit
> > the already posted patch, something else?
> 
> ...I suppose the problem with adding extra conditions to the expander
> is that it would break cases where the expander is used for target
> built-ins too.
> 
> Maybe optabs shouldn't be used for built-ins if the usage conditions
> aren't the same.  But if that's fighting too much against existing usage,
> the hook "hack" could check these conditions too.

Yeah, I'm aware that the target builtins use those expanders with the
current conditions and so would need to be renamed to something different
if we take the approach of adding the conditions to all rsqrt* expanders.

So, maybe it is best if I just apply my original patch right away so that
the bug is fixed and we can continue discussions on how we want to handle
it.

	Jakub

  reply	other threads:[~2015-11-30 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 22:25 Jakub Jelinek
2015-11-28  7:50 ` Richard Biener
2015-11-28  9:37   ` Jakub Jelinek
2015-11-28 11:02     ` Richard Biener
2015-11-30 14:30     ` Jakub Jelinek
2015-11-30 14:36       ` Richard Sandiford
2015-11-30 14:43         ` Jakub Jelinek [this message]
2015-11-30 15:03           ` Richard Biener
2015-12-01  5:09 ` Bin.Cheng

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=20151130143644.GE5675@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).