public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111714] Strange behavior when casting std::size_t to bool, UB or compiler bug? Date: Fri, 06 Oct 2023 15:19:38 +0000 [thread overview] Message-ID: <bug-111714-4-1s8hCwwJsv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111714-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111714 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- From IV-OPTs dup: inv_expr 3: (-(<unnamed-signed:1>) _13 - (<unnamed-signed:1>) &input) - -1 inv_expr 4: -(<unnamed-signed:1>) _13 - (<unnamed-signed:1>) &input That is totally bogus (that was even in GCC 8)
next prev parent reply other threads:[~2023-10-06 15:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-06 13:59 [Bug c++/111714] New: " carlosgalvezp at gmail dot com 2023-10-06 15:02 ` [Bug c++/111714] " rguenth at gcc dot gnu.org 2023-10-06 15:19 ` pinskia at gcc dot gnu.org [this message] 2023-10-06 16:25 ` [Bug tree-optimization/111714] " carlosgalvezp at gmail dot com 2023-10-06 16:26 ` pinskia 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-111714-4-1s8hCwwJsv@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: linkBe 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).