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/103268] [12 regression] ICE om glib-2.10.1: internal compiler error: in optimize_atomic_bit_test_and, at tree-ssa-ccp.c:3626
Date: Tue, 16 Nov 2021 03:24:17 +0000	[thread overview]
Message-ID: <bug-103268-4-GQAtT2xDnb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103268-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:074ee8d9a91d7573c1e8774a22e4e08f923adb18

commit r12-5290-g074ee8d9a91d7573c1e8774a22e4e08f923adb18
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Nov 15 17:37:10 2021 -0800

    Add a missing return when transforming atomic bit test and operations

    When failing to transform equivalent, but slighly different cases of
    atomic bit test and operations to their canonical forms, return
    immediately.

    gcc/

            PR middle-end/103268
            * tree-ssa-ccp.c (optimize_atomic_bit_test_and): Add a missing
            return.

    gcc/testsuite/

            PR middle-end/103268
            * gcc.dg/pr103268-1.c: New test.
            * gcc.dg/pr103268-2.c: Likewise.

  parent reply	other threads:[~2021-11-16  3:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 23:47 [Bug tree-optimization/103268] New: " slyfox at gcc dot gnu.org
2021-11-15 23:50 ` [Bug tree-optimization/103268] " pinskia at gcc dot gnu.org
2021-11-16  0:04 ` hjl.tools at gmail dot com
2021-11-16  0:12 ` hjl.tools at gmail dot com
2021-11-16  0:24 ` hjl.tools at gmail dot com
2021-11-16  1:32 ` crazylht at gmail dot com
2021-11-16  3:24 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-16  3:24 ` hjl.tools at gmail dot com

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-103268-4-GQAtT2xDnb@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).