public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106907] gcc/config/rs6000/rs6000.cc:23155: strange expression ? Date: Wed, 07 Jun 2023 16:29:00 +0000 [thread overview] Message-ID: <bug-106907-4-6bggfVTFfr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106907-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106907 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by jeevitha <jeevitha@gcc.gnu.org>: https://gcc.gnu.org/g:dda4745eb1c9b063c6004baef54aa4cec97edf3d commit r13-7426-gdda4745eb1c9b063c6004baef54aa4cec97edf3d Author: Jeevitha Palanisamy <jeevitha@linux.ibm.com> Date: Tue Jun 6 06:19:02 2023 -0500 rs6000: Remove duplicate expression [PR106907] PR106907 has few warnings spotted from cppcheck. In that addressing duplicate expression issue here. Here the same expression is used twice in logical AND(&&) operation which result in same result so removing that. 2023-06-06 Jeevitha Palanisamy <jeevitha@linux.ibm.com> gcc/ PR target/106907 * config/rs6000/rs6000.cc (vec_const_128bit_to_bytes): Remove duplicate expression. (cherry picked from commit c4deccd44655c5d748dfed200a37f2b678c32fe8)
next prev parent reply other threads:[~2023-06-07 16:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-12 11:08 [Bug target/106907] New: " dcb314 at hotmail dot com 2022-09-12 11:14 ` [Bug target/106907] " dcb314 at hotmail dot com 2022-09-12 11:16 ` dcb314 at hotmail dot com 2022-09-12 11:28 ` schwab@linux-m68k.org 2023-05-30 15:43 ` jeevitha at gcc dot gnu.org 2023-06-06 11:22 ` cvs-commit at gcc dot gnu.org 2023-06-07 16:29 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-09 8:49 ` cvs-commit at gcc dot gnu.org 2023-07-05 7:10 ` jeevitha at gcc dot gnu.org 2023-07-06 4:53 ` cvs-commit at gcc dot gnu.org 2023-10-30 10:43 ` cvs-commit at gcc dot gnu.org 2024-02-27 15:26 ` jeevitha 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-106907-4-6bggfVTFfr@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: 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).