public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: hongtao Liu <liuhongt@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5535] Fix typo in r12-5486. Date: Fri, 26 Nov 2021 00:59:25 +0000 (GMT) [thread overview] Message-ID: <20211126005925.4CF4F385841A@sourceware.org> (raw) https://gcc.gnu.org/g:379be00f45f65e0e8de72a50553dd9d2bab6cc08 commit r12-5535-g379be00f45f65e0e8de72a50553dd9d2bab6cc08 Author: liuhongt <hongtao.liu@intel.com> Date: Thu Nov 25 13:51:57 2021 +0800 Fix typo in r12-5486. gcc/ChangeLog: PR middle-end/103419 * match.pd: Fix typo, use the type of second parameter, not first one. Diff: --- gcc/match.pd | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/gcc/match.pd b/gcc/match.pd index fbb5a5a1eeb..e14f97ee1cd 100644 --- a/gcc/match.pd +++ b/gcc/match.pd @@ -4055,7 +4055,7 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT) } (if (ibit == ibit2 && ibit >= 0 - && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2)))))) + && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@0)))))) (match (nop_atomic_bit_test_and_p @0 @1 @3) (bit_and (convert?@3 (SYNC_FETCH_OR_XOR_N @2 INTEGER_CST@0)) @@ -4066,21 +4066,21 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT) } (if (ibit == ibit2 && ibit >= 0 - && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2)))))) + && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@0)))))) (match (nop_atomic_bit_test_and_p @0 @0 @4) (bit_and:c (convert1?@4 (ATOMIC_FETCH_OR_XOR_N @2 (nop_convert? (lshift@0 integer_onep@5 @6)) @3)) (convert2? @0)) - (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2))))) + (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@0))))) (match (nop_atomic_bit_test_and_p @0 @0 @4) (bit_and:c (convert1?@4 (SYNC_FETCH_OR_XOR_N @2 (nop_convert? (lshift@0 integer_onep@3 @5)))) (convert2? @0)) - (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2))))) + (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@0))))) (match (nop_atomic_bit_test_and_p @0 @1 @3) (bit_and@4 (convert?@3 (ATOMIC_FETCH_AND_N @2 INTEGER_CST@0 @5)) @@ -4092,7 +4092,7 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT) } (if (ibit == ibit2 && ibit >= 0 - && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2)))))) + && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@0)))))) (match (nop_atomic_bit_test_and_p @0 @1 @3) (bit_and@4 @@ -4105,21 +4105,21 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT) } (if (ibit == ibit2 && ibit >= 0 - && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2)))))) + && TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@0)))))) (match (nop_atomic_bit_test_and_p @4 @0 @3) (bit_and:c (convert1?@3 (ATOMIC_FETCH_AND_N @2 (nop_convert?@4 (bit_not (lshift@0 integer_onep@6 @7))) @5)) (convert2? @0)) - (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2))))) + (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@4))))) (match (nop_atomic_bit_test_and_p @4 @0 @3) (bit_and:c (convert1?@3 (SYNC_FETCH_AND_AND_N @2 (nop_convert?@4 (bit_not (lshift@0 integer_onep@6 @7))))) (convert2? @0)) - (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@2))))) + (if (TYPE_PRECISION (type) <= TYPE_PRECISION (TREE_TYPE (@4))))) #endif
reply other threads:[~2021-11-26 0:59 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=20211126005925.4CF4F385841A@sourceware.org \ --to=liuhongt@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).