Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] gdb.c++/templates.exp, pr gdb/1063
Date: Wed, 26 Feb 2003 01:15:00 -0000	[thread overview]
Message-ID: <200302260115.h1Q1FNl15043@duracef.shout.net> (raw)

David C writes:

> Hmm.  I guess, for now, just leaving the HP regexps in place is
> correct.

That sounds good to me.

I have heard that HP has a new compiler which follows the multi-vendor
standard C++ ABI.  In my dreams, that means that the gcc v3 code will
work with that new compiler.

At some point we'll have to face the HP music.

> So my current plan is to leave the HP regexps (but add a comment), to
> PASS the case where GDB can't print out the type info, to KFAIL the
> case where GDB incorrectly prints out one of the specializations (with
> reference to a nested types PR), and to close PR gdb/1063 (with an
> appropriate comment).  How does that sound?

Again that sounds good to me.

The old style was to use gdb_test as much as possible.  But I actually
like this new multi-armed gdb_expect style.  Maybe when things calm down
we can move to Daniel's new gdb_test_multiple, too.

I'll be reviewing the patch later this evening after I re-do my
HAVE_UINTPTR_T patch.

Michael C


             reply	other threads:[~2003-02-26  1:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  1:15 Michael Elizabeth Chastain [this message]
2003-02-26  1:23 ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2003-02-26  2:00 Michael Elizabeth Chastain
2003-02-26  0:35 David Carlton
2003-02-26  0:15 ` Daniel Jacobowitz
2003-02-26  1:35   ` David Carlton
2003-02-26  0:34     ` Daniel Jacobowitz
2003-02-26  1:03       ` David Carlton
2003-02-26 20:27         ` 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=200302260115.h1Q1FNl15043@duracef.shout.net \
    --to=mec@shout.net \
    --cc=carlton@math.stanford.edu \
    --cc=drow@mvista.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