Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@www.cgsoftware.com>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: David Taylor <taylor@candd.org>, <gdb-patches@sources.redhat.com>,
	Anthony Green <green@redhat.com>
Subject: Re: RFA: abstract C++ ABI dependencies
Date: Tue, 24 Apr 2001 16:23:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0104241921070.21119-100000@www.cgsoftware.com> (raw)
In-Reply-To: <nphezeylk4.fsf@zwingli.cygnus.com>

On 24 Apr 2001, Jim Blandy wrote:

>
> Thanks for reading so carefully (and promptly!).  I thought I'd been
> careful, but clearly there's a bunch of stuff botched.  I'll post a
> revision in a bit.
>
> I've answered your questions below.
>
> David Taylor <taylor@candd.org> writes:
> > cp-abi.h -- includes defs.h and value.h; this is contrary to the value
> > of the macro definition of cp_abi_h in Makefile.in.
> >
> > While I dislike having include files include other include files and I
> > don't wish to reopen that debate, I must ask -- why does cp-abi.h
> > include defs.h?
> >
> > Your definition of cp_abi_h is simply cp-abi.h -- however, cp-abi.h
> > includes other header files -- OOPS!
>
> I share your preference.  In the next rev of this patch, cp-abi.h will
> no longer #include any other files.

>
> >     2001-04-24  Jim Blandy  <jimb@redhat.com>
> >
> > 	    (Changes from Daniel Berlin, with revisions by Jim Blandy.)
> >
> > 	    Abstract out operations specific to particular C++ ABI's, and
> > 	    invoke them through a function table.  This removes the C++ ABI
> > 	    dependencies scattered throughout the code, and allows us to
> > 	    cleanly add support for new C++ ABI's.
> >
> > 	    * cp-abi.h, cp-abi.h, gnu-v2-abi.c, hpacc-abi.c: New files.
> >
> > *NONE* of these files initialize the rtti_type field within the
> > cp_abi_ops structure; they all let it default to 0.

This is normal, actually.
gnuv-2's rtti type is broken
Until the HP stuff is verified to work, it  avoids problems.

the v3 abi stuff defines an rtti_type that works okay.

> >
> > 	    * c-typeprint.c, c-valprint.c, dbxread.c, eval.c, gdbtypes.c,
> > 	    jv-typeprint.c, linespec.c, symtab.c, typeprint.c, valops.c:
> > 	    #include "cp-abi.h".
> >
> > For c-valprint.c, eval.c, typeprint.c, and valops.c, it is unclear to
> > me why you are including cp-abi.h.
>
> Because they use functions which used to be declared elsewhere, but
> are now declared in cp-abi.h.  I've clarified the ChangeLog entry.
>


  reply	other threads:[~2001-04-24 16:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 12:27 David Taylor
2001-04-24 15:33 ` Jim Blandy
2001-04-24 16:23   ` Daniel Berlin [this message]
2001-04-24 18:27     ` Jim Blandy
2001-04-24 23:21   ` Eli Zaretskii
2001-04-24 23:35     ` Daniel Berlin
2001-04-24 23:52       ` Eli Zaretskii
2001-04-25  0:07         ` Daniel Berlin
2001-04-25  0:24           ` Eli Zaretskii
2001-04-24 17:42 ` Jim Blandy
2001-04-25  5:04   ` Anthony Green
  -- strict thread matches above, loose matches on Subject: below --
2001-04-25  6:40 David Taylor
2001-04-26 17:23 ` Jim Blandy
2001-04-24 10:30 Jim Blandy

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=Pine.LNX.4.33.0104241921070.21119-100000@www.cgsoftware.com \
    --to=dan@www.cgsoftware.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=green@redhat.com \
    --cc=jimb@zwingli.cygnus.com \
    --cc=taylor@candd.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