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>,
	gdb-patches@sources.redhat.com, gilliam@us.ibm.com,
	manjo@austin.ibm.com
Subject: Re: about how to add support to new c++ compiler in GDB
Date: Wed, 27 Apr 2005 20:09:00 -0000	[thread overview]
Message-ID: <20050427200901.GA25180@nevyn.them.org> (raw)
In-Reply-To: <20050426031822.GA4998@nevyn.them.org>

On Mon, Apr 25, 2005 at 11:18:23PM -0400, Daniel Jacobowitz wrote:
> On Tue, Apr 26, 2005 at 10:53:03AM +0800, Wu Zhou wrote:
> > Hello Daniel and all,
> > 
> > I am recently running GDB testsuite against IBM's xlc compiler, and found
> > some problems with c++ testcases, especially while handling virtual-table
> > related stuff. After some analysis, I found there are some difference
> > between the debuginfo output between xlc++ and g++. The main difference I
> > noted now is that the class in xlc++ didn't depend on DW_TAG_containing_type
> > to find its virutal function table. Instead, every virtual class in xlc++
> > had its own "__vfp", which act the same role as "_vptr.CLASSNAME" in g++.
> > This will make gdb crash (SEGV) on quite a few c++ testcase.
> 
> I have some patches for this, originally developed for the ARM RVCT
> compiler.  I haven't had the time to clean them up and post them.
> They will probably be helpful to you.
> 
> If I haven't posted them by the end of this week, please, remind me.

You can find the patch, against current CVS GDB, at:
  http://return.false.org/~drow/gdb/combined-rvct-patches.diff

On i386-linux, using g++, it breaks a couple of gcj tests (hmm, I
thought I'd fixed that) and fixes a couple of C++ KFAILs.  For RVCT the
results are more dramatic.  It is going to be a long time before these
patches are all merged; there are 41 of them, some will require
discussion, and all will require me finding some time.  I'll go do the
first one now.

You should give these a try with xlc++ and see if they help.  If not,
we'll need to discuss the differences in xlc output.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-04-27 20:09 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
2005-04-27 20:09   ` Daniel Jacobowitz [this message]
     [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=20050427200901.GA25180@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gilliam@us.ibm.com \
    --cc=manjo@austin.ibm.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