From: "Doug Kwan (關振德)" <dougkwan@google.com>
To: gcc@gcc.gnu.org, gdb@sourceware.org
Subject: Adding new dwarf encoding formats for complex integers
Date: Fri, 14 Dec 2007 22:30:00 -0000 [thread overview]
Message-ID: <498552560712141430q75098aaembcda8db5c6edd8fb@mail.gmail.com> (raw)
Hi,
I am working on the gcc LTO project and I found that gcc does not
generate sufficient debugging information for complex integer types.
Currently gcc uses encoding DW_ATE_lo_user ( 0x80) for complex integer
types but that 1) clashes with an HP extension and 2) does not
distinguish between complex signed integer and complex unsigned
integer types. I'm thinking about adding DW_ATE_GNU_complex_signed
(0x87) and DW_ATE_GNU_complex_unsigned (0x88) encoding formats.
Is there anything I need to do in addition to changing gcc? Are
there people I should talk to? And what documentation should be
updated? Currently gdb (I checked 6.7) does not support complex
integer properly. So it needs to be changed anyway.
-Doug
next reply other threads:[~2007-12-14 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 22:30 Doug Kwan (關振德) [this message]
2007-12-14 22:35 ` Daniel Jacobowitz
2007-12-14 22:47 ` Doug Kwan (關振德)
2007-12-15 4:45 ` Daniel Jacobowitz
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=498552560712141430q75098aaembcda8db5c6edd8fb@mail.gmail.com \
--to=dougkwan@google.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.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).