public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Marc Poulhi?s <dkm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-1121] ada: Remove redundant parentheses from System.Stack_Checking.Operations
Date: Tue, 23 May 2023 08:08:28 +0000 (GMT)	[thread overview]
Message-ID: <20230523080828.3974F3857345@sourceware.org> (raw)

https://gcc.gnu.org/g:b0245ee3b3729fb961d203a580f21ecc49efb197

commit r14-1121-gb0245ee3b3729fb961d203a580f21ecc49efb197
Author: Patrick Bernardi <bernardi@adacore.com>
Date:   Tue Feb 28 17:30:46 2023 -0500

    ada: Remove redundant parentheses from System.Stack_Checking.Operations
    
    gcc/ada/
    
            * libgnat/s-stchop.adb (Stack_Check): Remove redundant parentheses.

Diff:
---
 gcc/ada/libgnat/s-stchop.adb | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/gcc/ada/libgnat/s-stchop.adb b/gcc/ada/libgnat/s-stchop.adb
index 8d8cc60ffb0..e0efcefa217 100644
--- a/gcc/ada/libgnat/s-stchop.adb
+++ b/gcc/ada/libgnat/s-stchop.adb
@@ -234,11 +234,10 @@ package body System.Stack_Checking.Operations is
          --  it is essential to use our local copy of Stack.
 
       begin
-         if (Stack_Grows_Down and then
-               (not (Frame_Address <= My_Stack.Base)))
+         if (Stack_Grows_Down and then not (Frame_Address <= My_Stack.Base))
            or else
             (not Stack_Grows_Down and then
-               (not (Frame_Address >= My_Stack.Base)))
+               not (Frame_Address >= My_Stack.Base))
          then
             --  The returned Base is lower than the stored one, so assume that
             --  the original one wasn't right and use the current Frame_Address

                 reply	other threads:[~2023-05-23  8:08 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=20230523080828.3974F3857345@sourceware.org \
    --to=dkm@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).