This is the mail archive of the
mailing list for the GDB project.
Re: RFC: C++ overloadin fixes and a type "char" tweak
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Fri, 10 Jan 2003 16:05:54 -0500
- Subject: Re: RFC: C++ overloadin fixes and a type "char" tweak
- References: <200301090506.h0956YI24933@duracef.shout.net>
On Wed, Jan 08, 2003 at 11:06:34PM -0600, Michael Elizabeth Chastain wrote:
> Hey, I've read this code recently!
> gdb fails overload resolution with TYPE_CODE_INT types
> Proofread but not tested. The gdb.c++/overload.exp part is approved
> no matter what. Those setup_xfail's are a flat lie, GDB has correct
> information and then makes the wrong overload choice on its own.
> The gdb part looks fine to me but I don't have resources to test it
> for a while.
Yep, thanks for pointing out the PR. You can't actually use
TYPE_UNSIGNED and TYPE_LENGTH; int -> long requires a promotion even if
they're the same size. Such is life in C++-ville.
I'll give it another couple of days in case anyone has a comment about
the way I special-case "char".
MontaVista Software Debian GNU/Linux Developer