public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Simon Marchi <>
Cc: Tom Tromey <>,
Subject: Re: [PATCH 2/2] Handle range types in ax-gdb.c
Date: Mon, 09 Jan 2023 09:11:11 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Simon Marchi's message of "Fri, 6 Jan 2023 16:51:32 -0500")

>>>>> "Simon" == Simon Marchi <> writes:

Simon> On 1/4/23 11:44, Tom Tromey via Gdb-patches wrote:
>> A range type can usually be treated the same as its underlying integer
>> type, at least for the purposes of agent expressions.  This patch
>> arranges for range types to be handled this way in ax-gdb.c, letting a
>> somewhat larger subset of Ada expressions be compiled.

Simon> Instead of stripping the range type at many places (possibly forgetting
Simon> some), I wonder if this could be done systematically before, when we
Simon> build the axs_values.

I didn't really consider this option, but now when looking at it, it
seems there are many more places that assign to 'type'.


  reply	other threads:[~2023-01-09 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 16:44 [PATCH 0/2] Add some agent expression support for Ada Tom Tromey
2023-01-04 16:44 ` [PATCH 1/2] Implement some agent expressions " Tom Tromey
2023-01-06 21:38   ` Simon Marchi
2023-01-09 15:49     ` Tom Tromey
2023-01-04 16:44 ` [PATCH 2/2] Handle range types in ax-gdb.c Tom Tromey
2023-01-06 21:51   ` Simon Marchi
2023-01-09 16:11     ` Tom Tromey [this message]
2023-02-27 15:03 ` [PATCH 0/2] Add some agent expression support for Ada Tom Tromey

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).