Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: PATCH to stabsread.c:read_member_functions
Date: Thu, 17 Jan 2002 07:14:00 -0000	[thread overview]
Message-ID: <20020117101455.A31202@nevyn.them.org> (raw)
In-Reply-To: <wvlk7uh819y.fsf@prospero.cambridge.redhat.com>

On Thu, Jan 17, 2002 at 03:06:49PM +0000, Jason Merrill wrote:
> This patch fixes gdb.c++/classes.exp:ptype Static when used with gcc 3.x
> and stabs output.  The code in question was never correct, just a likely
> guess; in particular, it got things wrong even with the v2 output for
> Static::ii, where the plain function name ("ii") was the same as the
> mangled form of the argument list (int, int == "ii").  For v3, we don't try
> to do minimal output, so it will always guess wrong.
> 
> OK?  Should I just remove the bad code rather than comment it out?
> 
> 2002-01-17  Jason Merrill  <jason@redhat.com>
> 
> 	* stabsread.c (read_member_functions): Never guess that the given
> 	physname for a static member function is a stub.
> 

Not OK, I think.  v2 -does- do minimal output, right?  We are not
dropping v2 support.

I've been meaning to fix this since I added the test.  The proper fix
might be to either:
 - know when to expect minimal output.  Does v2 ever not do it?  What
about other C++ compilers?
 - Check if it is a valid mangled name.  Will that work - can the
argument list ever be a valid mangled name in its own right?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-01-17 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17  7:07 Jason Merrill
2002-01-17  7:14 ` Daniel Jacobowitz [this message]
2002-01-17  7:15 ` Daniel Jacobowitz

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=20020117101455.A31202@nevyn.them.org \
    --to=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