public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105075] [nvptx] Generate sad insn (sum of absolute differences)
Date: Mon, 28 Mar 2022 13:15:18 +0000 [thread overview]
Message-ID: <bug-105075-4-XYCOe5vG2e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105075-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105075
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 28 Mar 2022, vries at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105075
>
> --- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
> Created attachment 52698
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52698&action=edit
> Demonstrator patch with stepping stone patterns for combine
>
> (In reply to Tom de Vries from comment #2)
> > Also, I wonder if defining a stepping-stone intermediate pattern could help
> > combine.
>
> Well, that approach seems to work.
Another possibility is to do this on GIMPLE where we detect widen
multiplication and friends
(tree-ssa-math-opts.cc:pass_optimize_widening_mul).
prev parent reply other threads:[~2022-03-28 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 7:53 [Bug target/105075] New: " vries at gcc dot gnu.org
2022-03-28 8:08 ` [Bug target/105075] " vries at gcc dot gnu.org
2022-03-28 8:13 ` vries at gcc dot gnu.org
2022-03-28 8:24 ` vries at gcc dot gnu.org
2022-03-28 9:50 ` tschwinge at gcc dot gnu.org
2022-03-28 10:15 ` rguenth at gcc dot gnu.org
2022-03-28 13:06 ` vries at gcc dot gnu.org
2022-03-28 13:15 ` rguenther at suse dot de [this message]
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=bug-105075-4-XYCOe5vG2e@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).