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++/107521] clang rejects invalid code in libstdc++ Date: Fri, 04 Nov 2022 04:27:35 +0000 [thread overview] Message-ID: <bug-107521-4-i3qW5pb3HV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107521-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107521 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The funny part is clang says: implementation-defined whether distinct literals will have distinct addresses In ____clang____, the result of such a comparison is unspecified, so it is not a constant expression. I think that means it is not a bug in either GCC nor clang. Just libstdc++ depends on GCC (implementation defined) behavior here ...
next prev parent reply other threads:[~2022-11-04 4:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-04 4:17 [Bug c++/107521] New: " tim at klingt dot org 2022-11-04 4:27 ` pinskia at gcc dot gnu.org [this message] 2022-11-04 4:29 ` [Bug c++/107521] " pinskia at gcc dot gnu.org 2022-11-04 8:17 ` jakub at gcc dot gnu.org 2022-11-04 8:26 ` jakub 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-107521-4-i3qW5pb3HV@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).