public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/99212] [11 Regression] gcc.dg/analyzer/data-model-1.c line 971
Date: Thu, 25 Feb 2021 23:03:48 +0000 [thread overview]
Message-ID: <bug-99212-4-mVKaeWW7zJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99212-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99212
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #2)
> x86_64-pc-linux-gnu has:
I messed up the copy and paste here; the x86_64 gimple actually reads:
bits.b0 = 1;
_1 = BIT_FIELD_REF <bits, 8, 0>;
_2 = _1 & 1;
_3 = _2 != 0;
_4 = (int) _3;
__analyzer_eval (_4);
bits.b456 = 5;
_5 = BIT_FIELD_REF <bits, 8, 0>;
_6 = _5 & 112;
_7 = _6 == 80;
_8 = (int) _7;
__analyzer_eval (_8);
next prev parent reply other threads:[~2021-02-25 23:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 3:35 [Bug analyzer/99212] New: " hp at gcc dot gnu.org
2021-02-23 8:27 ` [Bug analyzer/99212] " rguenth at gcc dot gnu.org
2021-02-23 14:49 ` hp at gcc dot gnu.org
2021-02-25 23:02 ` dmalcolm at gcc dot gnu.org
2021-02-25 23:03 ` dmalcolm at gcc dot gnu.org [this message]
2021-02-26 12:58 ` rguenth at gcc dot gnu.org
2021-02-26 14:23 ` dmalcolm at gcc dot gnu.org
2021-02-26 14:33 ` dmalcolm at gcc dot gnu.org
2021-04-04 21:57 ` hp at gcc dot gnu.org
2021-04-09 8:24 ` rguenth at gcc dot gnu.org
2021-04-09 23:11 ` hp at gcc dot gnu.org
2021-04-10 17:45 ` dmalcolm at gcc dot gnu.org
2021-04-12 12:59 ` dmalcolm at gcc dot gnu.org
2021-04-13 2:23 ` hp at gcc dot gnu.org
2021-04-13 2:23 ` cvs-commit at gcc dot gnu.org
2021-04-27 11:40 ` [Bug analyzer/99212] [11/12 " jakub at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2021-06-08 18:46 ` cvs-commit at gcc dot gnu.org
2021-06-08 19:30 ` [Bug analyzer/99212] [11 " dmalcolm at gcc dot gnu.org
2021-06-15 8:05 ` stefansf at linux dot ibm.com
2021-06-15 14:28 ` dmalcolm at gcc dot gnu.org
2021-06-15 21:54 ` cvs-commit at gcc dot gnu.org
2021-06-18 7:36 ` stefansf at linux dot ibm.com
2021-07-02 19:22 ` cvs-commit at gcc dot gnu.org
2021-07-02 19:22 ` cvs-commit at gcc dot gnu.org
2021-07-02 19:31 ` dmalcolm 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-99212-4-mVKaeWW7zJ@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).