public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/115272] [debug] complex type is hard to related back to base type
Date: Wed, 29 May 2024 11:18:22 +0000	[thread overview]
Message-ID: <bug-115272-4-InFKhfQKfD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115272-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115272

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
How does it work for 'double' vs. 'long double' themselves?

 <1><32>: Abbrev Number: 3 (DW_TAG_base_type)
    <33>   DW_AT_byte_size   : 16
    <34>   DW_AT_encoding    : 4        (float)
    <35>   DW_AT_name        : (indirect string, offset: 0x60): long double

so if it's not distinguishable via DW_AT_byte_size you look into
DW_AT_name as well?  So it looks like doing the same for _Complex long double
is perfectly in line?

  reply	other threads:[~2024-05-29 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29  9:49 [Bug debug/115272] New: " vries at gcc dot gnu.org
2024-05-29 11:18 ` rguenth at gcc dot gnu.org [this message]
2024-05-29 11:19 ` [Bug debug/115272] " rguenth at gcc dot gnu.org
2024-05-29 12:03 ` vries at gcc dot gnu.org
2024-05-29 12:08 ` vries at gcc dot gnu.org
2024-06-19 15:38 ` vries 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-115272-4-InFKhfQKfD@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: link
Be 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).