From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: RFC: Slay COERCE_FLOAT_TO_DOUBLE
Date: Wed, 08 Jan 2003 00:20:00 -0000 [thread overview]
Message-ID: <3E1B6E90.2010809@redhat.com> (raw)
In-Reply-To: <200301071800.h07I0H027120@duracef.shout.net>
> 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.
enjoy,
Andrew
next prev parent reply other threads:[~2003-01-08 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 18:05 Michael Elizabeth Chastain
2003-01-08 0:20 ` Andrew Cagney [this message]
2003-01-08 0:47 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 14:03 Daniel Jacobowitz
2002-12-24 11:39 ` Eli Zaretskii
2003-01-04 22:38 ` Daniel Jacobowitz
2003-01-06 22:43 ` Andrew Cagney
2003-01-07 18:16 ` 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=3E1B6E90.2010809@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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