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/111766] Missed optimization with __builtin_unreachable and ands
Date: Fri, 03 Nov 2023 17:14:12 +0000 [thread overview]
Message-ID: <bug-111766-4-5rfUtT1WBj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111766-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111766
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>:
https://gcc.gnu.org/g:7ab79a40b546a1470abaf76bec74c63e9990fe47
commit r14-5110-g7ab79a40b546a1470abaf76bec74c63e9990fe47
Author: Andrew MacLeod <amacleod@redhat.com>
Date: Wed Oct 25 09:46:50 2023 -0400
Adjust operators equal and not_equal to check bitmasks against constants
Check to see if a comparison to a constant can be determined to always
be not-equal based on the bitmask.
PR tree-optimization/111766
gcc/
* range-op.cc (operator_equal::fold_range): Check constants
against the bitmask.
(operator_not_equal::fold_range): Ditto.
* value-range.h (irange_bitmask::member_p): New.
gcc/testsuite/
* gcc.dg/pr111766.c: New.
next prev parent reply other threads:[~2023-11-03 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 1:55 [Bug tree-optimization/111766] New: " pinskia at gcc dot gnu.org
2023-10-11 14:00 ` [Bug tree-optimization/111766] " amacleod at redhat dot com
2023-11-03 17:14 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-03 17:15 ` amacleod at redhat dot com
2023-11-03 17:15 ` amacleod at redhat dot com
2023-11-03 17:29 ` sjames at gcc dot gnu.org
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-111766-4-5rfUtT1WBj@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).