public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uweigand 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: Mon, 25 Jul 2022 15:08:32 +0000 [thread overview] Message-ID: <bug-104194-4-xfXHIh2bNA@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 Ulrich Weigand <uweigand at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uweigand at gcc dot gnu.org --- Comment #8 from Ulrich Weigand <uweigand at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #7) > A temporary workaround now applied. It turns out this workaround is not transparent to users of the debugger, for example if you define a variable as long double x; and then issue the "ptype x" command in GDB, you'll now get "_Float128" - which is quite surprising if you've never even used that type in your source code. (This also causes a few GDB test suite failures.) > The dwarf-discuss thread seems to prefer using separate DW_ATE_* values > instead of DW_AT_precision/DW_AT_minimum_exponent, but hasn't converged yet. When I discussed this back in 2017: https://slideslive.com/38902369/precise-target-floatingpoint-emulation-in-gdb (see page 16 in the slides), my suggestion was simple DW_AT_encoding_variant which would have the let the details of the floating-point format remain platform-defined (unspecified by DWARF), but simply allow a platform to define multiple different formats of the same size if required.
prev parent reply other threads:[~2022-07-25 15:08 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 ` [Bug debug/104194] " segher at gcc dot gnu.org 2022-01-24 12:37 ` 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 [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-104194-4-xfXHIh2bNA@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).