Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: about how to add support to new c++ compiler in GDB
Date: Tue, 26 Apr 2005 13:20:00 -0000	[thread overview]
Message-ID: <20050426131718.GB24724@nevyn.them.org> (raw)
In-Reply-To: <01cf01c54a45$899fb070$7286b509@ibmcsdl9m89c83>

On Tue, Apr 26, 2005 at 05:51:34PM +0800, Wu Zhou wrote:
> I am not very sure. They(the developer of xlc) said that they also follow
> GNU V3 C++ ABI. But there are quite a few difference between the debuginfo
> generated by g++ and xlc++. An new file named xlc-abi.c is what I could
> thought of at this time. It could verify my idea, and at the same time not
> impact the debugging of g++ code. If the changes is not big, maybe we could
> integrate them back into gnu-v3-abi.c at last.

If the debugging information is different, you will need changes in the
dwarf2 reader.  However, you will probably not need a new ABI file; the
gnu-v3-abi code should suffice.

> My manager are arranging this for me. Do I need to assign any document
> myself? If yes, I am very glad to do so.

I don't know.  Let's see what happens.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-26 13:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26  2:54 Wu Zhou
2005-04-26  3:18 ` Daniel Jacobowitz
2005-04-26  9:53   ` Wu Zhou
2005-04-26 13:20     ` Daniel Jacobowitz [this message]
2005-04-27 20:09   ` Daniel Jacobowitz
     [not found]     ` <019101c54bc9$20360cd0$4186b509@ibmcsdl9m89c83>
     [not found]       ` <20050428131902.GB29277@nevyn.them.org>
2005-04-29  2:37         ` Wu Zhou
2005-04-29  7:28           ` Wu Zhou
2005-04-29 13:10             ` Daniel Jacobowitz
2005-04-28  6:34 woodzltc
2005-05-09 12:42 Wu Zhou

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=20050426131718.GB24724@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=woodzltc@cn.ibm.com \
    /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