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 preprocessor/112701] wrong type inference for ternary operator with `0/0u` in preprocessing context Date: Fri, 24 Nov 2023 15:46:45 +0000 [thread overview] Message-ID: <bug-112701-4-A4m5p7RSYW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112701-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112701 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Interesting is MSVC emits both. clang emits none.
next prev parent reply other threads:[~2023-11-24 15:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-24 14:56 [Bug preprocessor/112701] New: wrong type inference for ternary operator " amonakov at gcc dot gnu.org 2023-11-24 15:46 ` pinskia at gcc dot gnu.org [this message] 2023-11-25 17:06 ` [Bug preprocessor/112701] wrong type inference for ternary operator with `0/0u` " mikpelinux at gmail dot com 2023-11-27 7:56 ` rguenth at gcc dot gnu.org 2023-11-27 17:56 ` lhyatt at gcc dot gnu.org 2023-11-27 18:02 ` pinskia at gcc dot gnu.org 2023-11-28 0:14 ` lhyatt at gcc dot gnu.org 2023-11-28 2:44 ` cvs-commit at gcc dot gnu.org 2023-11-28 2:45 ` lhyatt at gcc dot gnu.org 2023-11-28 6:54 ` 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-112701-4-A4m5p7RSYW@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).