From: Daniel Jacobowitz <drow@false.org>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Extend some arithmetic operations to range types.
Date: Wed, 31 Mar 2004 19:05:00 -0000 [thread overview]
Message-ID: <20040331190517.GA5010@nevyn.them.org> (raw)
In-Reply-To: <20040329112951.08FBEF2F03@nile.gnat.com>
On Mon, Mar 29, 2004 at 06:29:51AM -0500, Paul Hilfinger wrote:
>
> Here is a second draft of the patch I submitted on 26 March. I
> believe I have addressed Daniel's comments. Rather than using a
> 'base_type' function to strip off range-type wrappers, I use the
> existing is_integral_type. This has the side-effect of extending some
> of the operations to work on BOOL or CHAR, which I am assuming is
> harmless. By using is_integral_type, we also can eliminate some calls
> to COERCE_ENUM. For consistency and to tidy things up a bit, I have
> taken the liberty of changing value_binop to also use is_integral_type.
>
> Comments?
>
> Paul Hilfinger
> ACT, Inc.
>
> 2004-03-26 Paul N. Hilfinger <Hilfinger@gnat.com>
>
> * valarith.c: Update copyright notice.
> (value_add): Handle range types.
> (value_sub): Ditto.
> (value_equal): Ditto.
> (value_less): Ditto.
> (value_neg): Ditto.
> (value_complement): Ditto.
> (value_binop): Simplify slightly by using is_integral_type and
> eliminiating unnecessary COERCE_ENUMs.
This patch looks good to me. Assuming that you've run the testsuite
with no regressions, it is OK.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-31 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 10:59 Paul Hilfinger
2004-03-26 18:07 ` Daniel Jacobowitz
2004-03-26 19:03 ` Joel Brobecker
2004-03-26 20:32 ` Daniel Jacobowitz
2004-03-29 11:29 ` Paul Hilfinger
2004-03-31 19:05 ` Daniel Jacobowitz [this message]
2004-04-01 12:11 ` Paul Hilfinger
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=20040331190517.GA5010@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.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