Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ezannoni@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/symtab/c++] fix c++ rtti type lookup
Date: Thu, 04 Dec 2003 21:38:00 -0000	[thread overview]
Message-ID: <20031204213849.717C74B35C@berman.michael-chastain.com> (raw)

eza> here is a quandary. Should we carry around such code if nobody uses
eza> it. If we cannot test it we might as well explicitly admit it.

We have a big issue here.

There are a lot of multi-user Unix systems that aren't getting tested
enough, or tested at all: aix, hpux, irix, solaris.  There are very few
posts to gdb-testers for those architectures.

When I clean up my mailbox and my back-log, I'm going to work on this.
I'm going to ask around for people who can give me ssh accounts on such
machines, or are willing to become volunteer testers.

mec> . Nested types give a warning and don't work.
mec>   It would be nice to make them work.
eza> is there a bug/testcase?

Yes, gdb.cp/local.exp.

eza> If you move the function to cp-support.c and cp-support.h I think you
eza> can avoid touching symtab.h altogether.

Right.  I put out a second version of the patch organized like that.
So you can discard the first version.

Michael C


             reply	other threads:[~2003-12-04 21:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 21:38 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-27  7:09 Michael Elizabeth Chastain
2003-12-01 17:13 ` David Carlton
2003-12-04 21:16 ` Elena Zannoni
2003-12-04 21:18   ` David Carlton

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=20031204213849.717C74B35C@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.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