public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96167] fails to detect ROL pattern in simple case, but succeeds when operand goes through memcpy
Date: Wed, 15 Jul 2020 13:57:43 +0000	[thread overview]
Message-ID: <bug-96167-4-2oRrFcJHBu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96167-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96167

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah.  But at least if the target has corresponding mode rotate optab, there is
no reason not to support any rotates by constant multiples of byte size (for
bit rotates we don't have infrastructure for that).

  parent reply	other threads:[~2020-07-15 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 16:10 [Bug tree-optimization/96167] New: " nok.raven at gmail dot com
2020-07-13  8:08 ` [Bug tree-optimization/96167] " rguenth at gcc dot gnu.org
2020-07-15 13:40 ` ebotcazou at gcc dot gnu.org
2020-07-15 13:57 ` jakub at gcc dot gnu.org [this message]
2020-07-15 14:04 ` jakub at gcc dot gnu.org
2023-08-04 22:26 ` pinskia at gcc dot gnu.org
2023-08-04 22:31 ` pinskia at gcc dot gnu.org

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-96167-4-2oRrFcJHBu@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).