Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: dan@www.cgsoftware.com, fnasser@cygnus.com, chastain@cygnus.com,
	fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] testsuite/gdb.c++/ref-types.exp: use runto
Date: Fri, 16 Mar 2001 14:43:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1010316143920.1096A-100000@cse.cygnus.com> (raw)
In-Reply-To: <200103162235.OAA06707@bosch.cygnus.com>

On Fri, 16 Mar 2001, Michael Elizabeth Chastain wrote:

> Daniel Berlin writes:
> > Insufficient information, too many possibilities, and
> > too much of a performance hit.
> 
> Well, I'll see the information for myself when I get to virtfunc.exp
> and see whether the stabs have sufficient information or not.
Sigh.

 > 
> As far as "too many possibilities" and "too much of a performance hit"
> goes: those are not good reasons for (a) the software to print wrong
> answers 

Um, what exactly *should* it print?

It doesn't know it's wrong.

You seem to not be getting how virtual function calling works. If we 
could tell we were wrong, we wouldn't have a problem in the first place.

Feel free to implement the code to make it work right, or determine its 
wrong.

With some patches i'm about to submit, the v3 abi passes all of 
virtfunc.cc, and I have no plans to write 1500 lines of code to handle 
all possible v2 cases.

>and then (b) the maintainers to  claim that the software isn't > broken.

Fine, mark them fail. Just put (Won't ever fix for v2 abi) in parentheses.


> 
> Michael
> 


  parent reply	other threads:[~2001-03-16 14:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-16 14:35 Michael Elizabeth Chastain
2001-03-16 14:40 ` Fernando Nasser
2001-03-16 14:43 ` Daniel Berlin [this message]
2001-03-16 14:44 ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2001-03-17 14:37 Michael Elizabeth Chastain
2001-03-17 12:42 Michael Elizabeth Chastain
2001-03-17 15:31 ` Daniel Berlin
2001-03-17 12:35 Michael Elizabeth Chastain
2001-03-17 14:23 ` Daniel Berlin
2001-03-16 21:00 Michael Elizabeth Chastain
2001-03-17 11:12 ` Daniel Berlin
2001-03-16 16:03 Michael Elizabeth Chastain
2001-03-16 14:50 Michael Elizabeth Chastain
2001-03-16 14:55 ` Daniel Berlin
2001-03-16 14:49 Michael Elizabeth Chastain
2001-03-16 14:55 ` Daniel Berlin
     [not found] ` <20010316215907.A3607@redhat.com>
2001-03-17 11:59   ` Daniel Berlin
2001-03-16 13:15 Michael Elizabeth Chastain
2001-03-16 13:21 ` Fernando Nasser
2001-03-16 15:14   ` Peter.Schauer
2001-03-16 15:17     ` Daniel Berlin
2001-03-16 15:45       ` Michael Snyder
2001-03-16 15:49         ` Daniel Berlin
2001-03-16 15:19   ` Andrew Cagney
2001-03-16 15:21     ` Daniel Berlin
2001-03-17  7:56   ` Daniel Berlin
     [not found] <200103161807.KAA06081@bosch.cygnus.com>
2001-03-16 12:00 ` Fernando Nasser
2001-03-16 13:00 ` Daniel Berlin
2001-03-16 14:29   ` Michael Snyder
2001-03-04 15:25 Michael Elizabeth Chastain
2001-02-24  0:16 Michael Elizabeth Chastain

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.SOL.3.91.1010316143920.1096A-100000@cse.cygnus.com \
    --to=dberlin@cygnus.com \
    --cc=chastain@cygnus.com \
    --cc=dan@www.cgsoftware.com \
    --cc=fnasser@cygnus.com \
    --cc=fnasser@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