public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Roger Sayle <sayle@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-5616] [Committed] PR testsuite/103477: Fix big-endian mistake in new test case.
Date: Tue, 30 Nov 2021 10:37:54 +0000 (GMT)	[thread overview]
Message-ID: <20211130103754.AE41A3858C2C@sourceware.org> (raw)

https://gcc.gnu.org/g:92de188ea3d36ec012b6d42959d4722e42524256

commit r12-5616-g92de188ea3d36ec012b6d42959d4722e42524256
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Tue Nov 30 10:25:35 2021 +0000

    [Committed] PR testsuite/103477: Fix big-endian mistake in new test case.
    
    I missed a spot when adding the "#if __BYTE_ORDER__ == ..." guards to
    the new test case for PR tree-optimization/103345.  Committed as obvious.
    
    2021-11-30  Roger Sayle  <roger@nextmovesoftware.com>
    
    gcc/testsuite/ChangeLog
            PR testsuite/103477
            * gcc.dg/tree-ssa/pr103345.c: Correct xor test for big-endian.

Diff:
---
 gcc/testsuite/gcc.dg/tree-ssa/pr103345.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/pr103345.c b/gcc/testsuite/gcc.dg/tree-ssa/pr103345.c
index 94388b541c1..dc8810ab5af 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/pr103345.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/pr103345.c
@@ -42,10 +42,10 @@ uint32_t load_le_32_xor(const uint8_t *ptr)
          ((uint32_t)ptr[2] << 16) ^
          ((uint32_t)ptr[3] << 24);
 #else
-  return ((uint32_t)ptr[0]) ^
-         ((uint32_t)ptr[1] << 8) ^
-         ((uint32_t)ptr[2] << 16) ^
-         ((uint32_t)ptr[3] << 24);
+  return ((uint32_t)ptr[3]) ^
+         ((uint32_t)ptr[2] << 8) ^
+         ((uint32_t)ptr[1] << 16) ^
+         ((uint32_t)ptr[0] << 24);
 #endif
 }


                 reply	other threads:[~2021-11-30 10:37 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=20211130103754.AE41A3858C2C@sourceware.org \
    --to=sayle@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).