public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/104194] No way to distinguish IEEE and IBM long double in debug info Date: Sun, 23 Jan 2022 18:51:19 +0000 [thread overview] Message-ID: <bug-104194-4-IjKae4Ipfu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104194-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104194 --- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> --- Maybe we should say what actual mode is used in the DWARF info, not the C way of getting there? So something that denotes DP / double-double / QP, for our three options for long double?
next prev parent reply other threads:[~2022-01-23 18:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-23 15:48 [Bug debug/104194] New: " jakub at gcc dot gnu.org 2022-01-23 18:51 ` segher at gcc dot gnu.org [this message] 2022-01-24 12:37 ` [Bug debug/104194] " jakub at gcc dot gnu.org 2022-01-24 17:46 ` jakub at gcc dot gnu.org 2022-01-24 18:55 ` jakub at gcc dot gnu.org 2022-01-24 21:48 ` segher at gcc dot gnu.org 2022-01-26 18:43 ` cvs-commit at gcc dot gnu.org 2022-01-26 18:46 ` jakub at gcc dot gnu.org 2022-07-25 15:08 ` uweigand 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-104194-4-IjKae4Ipfu@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).