From: Daniel Jacobowitz <drow@false.org>
To: "Doug Kwan (關振德)" <dougkwan@google.com>
Cc: gcc@gcc.gnu.org, gdb@sourceware.org
Subject: Re: Adding new dwarf encoding formats for complex integers
Date: Fri, 14 Dec 2007 22:35:00 -0000 [thread overview]
Message-ID: <20071214223532.GA11966@caradoc.them.org> (raw)
In-Reply-To: <498552560712141430q75098aaembcda8db5c6edd8fb@mail.gmail.com>
On Fri, Dec 14, 2007 at 02:30:36PM -0800, Doug Kwan (關振德) wrote:
> 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.
The DWARF standard has its own mailing list and working group. I
recommend contacting them first, to see if there's interest in a
general definition.
If you just want to add it to the GNU tools, then lo_user seems like
the best place to put it - it's a vendor extension - so I don't
see the problem.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-14 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 22:30 Doug Kwan (關振德)
2007-12-14 22:35 ` Daniel Jacobowitz [this message]
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=20071214223532.GA11966@caradoc.them.org \
--to=drow@false.org \
--cc=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