From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Richard Biener <rguenther@suse.de>,
Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Move negative stride bias out of dr_misalignment
Date: Tue, 26 Oct 2021 13:48:39 +0200 [thread overview]
Message-ID: <5916DAE9-2B77-4AA7-9676-BA2A8538A219@gmail.com> (raw)
In-Reply-To: <24qs317-4090-n6n6-1o2n-40r52no5313n@fhfr.qr>
On 26 October 2021 11:19:44 CEST, Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>@@ -2010,6 +2010,7 @@ get_negative_load_store_type (vec_info *vinfo,
> if (dump_enabled_p ())
> dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location,
> "negative step but alignment required.\n");
>+ *poffset = 0;
> return VMAT_ELEMENTWISE;
> *poffset = 0;
> }
I think you cannot really diagnose these, they would trigger a lot, in each early return, no?
Or would we see that there are unreachable, non artificial stmts in the same block after a return?
Somebody could experiment with diagnosing each and every DCEd stmt (!artificial, nondebug) but I would expect that hell breaks loose..
cheers,
next prev parent reply other threads:[~2021-10-26 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 9:19 Richard Biener
2021-10-26 11:48 ` Bernhard Reutner-Fischer [this message]
2021-10-26 12:10 ` Richard Biener
2021-10-26 12:25 ` Bernhard Reutner-Fischer
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=5916DAE9-2B77-4AA7-9676-BA2A8538A219@gmail.com \
--to=rep.dot.nop@gmail.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).