This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: RFC: Slay COERCE_FLOAT_TO_DOUBLE
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: Michael Elizabeth Chastain <mec at shout dot net>,gdb-patches at sources dot redhat dot com
- Date: Tue, 7 Jan 2003 19:47:53 -0500
- Subject: Re: RFC: Slay COERCE_FLOAT_TO_DOUBLE
- References: <200301071800.h07I0H027120@duracef.shout.net> <3E1B6E90.2010809@redhat.com>
On Tue, Jan 07, 2003 at 07:19:28PM -0500, Andrew Cagney wrote:
>
> >Daniel's patch keeps the current data structure, which uses 1 bit
> >to indicate whether the function is prototyped or not.
> >
> >I prefer to use 2 bits: TYPE_PROTO_KNOWN and TYPE_PROTO_YES.
> >That allows for three states:
> >
> > known=0 gdb does not know if function is prototyped
> > known=1, yes=0 function is definitely not prototyped
> > known=1, yes=1 function is definitely prototyped
> >
> >I have written such a 2-bit patch.
>
> To be pedantic :-) That's an enum with three states:
>
> prototype unknown
> prototyped
> unprototyped
>
> It can be packed into two bits.
If we want to go this way, then it should probably be done with four
states anyway:
User prototyped vs. not
Type is declared-as vs. called-as
I didn't do this because the usefulness of the extra information is
pretty minor; but we certainly could do it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer