public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Segher Boessenkool <segher@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2579] rs6000: Make an "if" statement more regular
Date: Sat, 10 Sep 2022 15:23:32 +0000 (GMT)	[thread overview]
Message-ID: <20220910152332.7E1F23858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:16d752a514033a9e37fed2a7f78024e222ca26b9

commit r13-2579-g16d752a514033a9e37fed2a7f78024e222ca26b9
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date:   Sat Sep 10 15:13:40 2022 +0000

    rs6000: Make an "if" statement more regular
    
    As Akari noticed, we have an unusual "if" statement without parentheses
    around the condition.  The condition is a macro that expands to
    something with parentheses in the right spot, but, let's make the code a
    little less surprising :-)
    
    2022-09-10  Akari Takahashi  <akaritakahashioss@gmail.com>
                Segher Boessenkool  <segher@kernel.crashing.org>
    
            * config/rs6000/rs6000.cc (get_memref_parts): Regularize some code.

Diff:
---
 gcc/config/rs6000/rs6000.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc
index a656cb32a47..bcf634a146d 100644
--- a/gcc/config/rs6000/rs6000.cc
+++ b/gcc/config/rs6000/rs6000.cc
@@ -18114,7 +18114,7 @@ get_memref_parts (rtx mem, rtx *base, HOST_WIDE_INT *offset,
 		  HOST_WIDE_INT *size)
 {
   rtx addr_rtx;
-  if MEM_SIZE_KNOWN_P (mem)
+  if (MEM_SIZE_KNOWN_P (mem))
     *size = MEM_SIZE (mem);
   else
     return false;

                 reply	other threads:[~2022-09-10 15:23 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=20220910152332.7E1F23858D32@sourceware.org \
    --to=segher@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: 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).