public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4378] Fix comment for (A / (1 << B)) -> (A >> B). Date: Mon, 28 Nov 2022 20:13:50 +0000 (GMT) [thread overview] Message-ID: <20221128201350.3480C3858C62@sourceware.org> (raw) https://gcc.gnu.org/g:47d81b1b89d615cea27307c713a4afe591e1cd2d commit r13-4378-g47d81b1b89d615cea27307c713a4afe591e1cd2d Author: Andrew Pinski <apinski@marvell.com> Date: Mon Nov 28 20:10:28 2022 +0000 Fix comment for (A / (1 << B)) -> (A >> B). There was a small typo where Also was done twice. The second also should have been handled. This fixes that. Committed as obvious after a build. gcc/ChangeLog: * match.pd ((A / (1 << B)) -> (A >> B).): Fix comment. Diff: --- gcc/match.pd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/match.pd b/gcc/match.pd index 67a0a682f31..f8610e37011 100644 --- a/gcc/match.pd +++ b/gcc/match.pd @@ -354,7 +354,7 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT) Only for unsigned A. For signed A, this would not preserve rounding toward zero. For example: (-1 / ( 1 << B)) != -1 >> B. - Also also widening conversions, like: + Also handle widening conversions, like: (A / (unsigned long long) (1U << B)) -> (A >> B) or (A / (unsigned long long) (1 << B)) -> (A >> B).
reply other threads:[~2022-11-28 20:13 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221128201350.3480C3858C62@sourceware.org \ --to=pinskia@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).