public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108934] [12 Regression] bit_cast'ing to long double errors out with "the argument cannot be interpreted" since gcc-12 Date: Mon, 20 Mar 2023 10:28:22 +0000 [thread overview] Message-ID: <bug-108934-4-egVu2lCa3N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108934-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108934 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Fixed for 12.3 too.
prev parent reply other threads:[~2023-03-20 10:28 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-25 22:58 [Bug c++/108934] New: " janpmoeller at gmx dot de 2023-02-25 23:09 ` [Bug c++/108934] " pinskia at gcc dot gnu.org 2023-02-25 23:09 ` pinskia at gcc dot gnu.org 2023-02-25 23:11 ` pinskia at gcc dot gnu.org 2023-02-25 23:15 ` pinskia at gcc dot gnu.org 2023-03-01 15:56 ` jakub at gcc dot gnu.org 2023-03-01 15:57 ` [Bug c++/108934] [12/13 Regression] " jakub at gcc dot gnu.org 2023-03-01 16:02 ` jakub at gcc dot gnu.org 2023-03-01 16:19 ` jakub at gcc dot gnu.org 2023-03-02 8:28 ` cvs-commit at gcc dot gnu.org 2023-03-02 8:29 ` [Bug c++/108934] [12 " jakub at gcc dot gnu.org 2023-03-19 5:30 ` cvs-commit at gcc dot gnu.org 2023-03-20 10:28 ` jakub at gcc dot gnu.org [this message]
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-108934-4-egVu2lCa3N@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).