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 tree-optimization/103345] missed optimization: add/xor individual bytes to form a word
Date: Tue, 30 Nov 2021 10:37:55 +0000	[thread overview]
Message-ID: <bug-103345-4-3qlqhAEe0f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103345-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103345

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

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.

      parent reply	other threads:[~2021-11-30 10:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-21 11:17 [Bug other/103345] New: " gcc at rjk dot terraraq.uk
2021-11-21 12:44 ` [Bug tree-optimization/103345] " roger at nextmovesoftware dot com
2021-11-22  8:41 ` roger at nextmovesoftware dot com
2021-11-22 18:17 ` cvs-commit at gcc dot gnu.org
2021-11-24  8:55 ` cvs-commit at gcc dot gnu.org
2021-11-25 19:47 ` roger at nextmovesoftware dot com
2021-11-30 10:37 ` cvs-commit at gcc dot gnu.org [this message]

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-103345-4-3qlqhAEe0f@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: 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).