From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 4/4] gdb: fix value_subscript when array upper bound is not known
Date: Wed, 9 Dec 2020 14:57:53 -0500 [thread overview]
Message-ID: <a2931944-a355-84c8-4c8f-f4e9b389a41a@polymtl.ca> (raw)
In-Reply-To: <20201206075437.GC327270@adacore.com>
On 2020-12-06 2:54 a.m., Joel Brobecker wrote:
> Other than that, the change looks OK to me.
>
> I believe, between the impact of the fix, the fact that it is
> a recent regression, and the relatively straightforward nature
> of your patch series, I believe it will be safe to backport to
> the gdb-10-branch.
FYI, I pushed this to the master branch, and I am in the process of
backporting it to the gdb-10-branch. There are a few conflicts, so
I'll give it a test run before pushing it there.
Simon
prev parent reply other threads:[~2020-12-09 19:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 16:21 [PATCH 0/4] Fix bug in value_subscript when range's high " Simon Marchi
2020-11-23 16:21 ` [PATCH 1/4] gdb: make discrete_position return optional Simon Marchi
2020-12-06 5:25 ` Joel Brobecker
2020-12-06 5:38 ` Joel Brobecker
2020-12-07 14:58 ` Simon Marchi
2020-12-08 3:06 ` Joel Brobecker
2020-12-08 11:41 ` Maciej W. Rozycki
2020-12-09 19:29 ` Simon Marchi
2020-12-09 19:53 ` Maciej W. Rozycki
2020-11-23 16:21 ` [PATCH 2/4] gdb: make get_discrete_bounds return bool Simon Marchi
2020-12-06 6:03 ` Joel Brobecker
2020-12-07 15:19 ` Simon Marchi
2020-11-23 16:21 ` [PATCH 3/4] gdb: split get_discrete_bounds in two Simon Marchi
2020-12-06 7:29 ` Joel Brobecker
2020-12-07 15:49 ` Simon Marchi
2020-11-23 16:21 ` [PATCH 4/4] gdb: fix value_subscript when array upper bound is not known Simon Marchi
2020-12-06 7:54 ` Joel Brobecker
2020-12-07 16:06 ` Simon Marchi
2020-12-08 3:14 ` Joel Brobecker
2020-12-09 18:50 ` Simon Marchi
2020-12-09 19:57 ` Simon Marchi [this message]
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=a2931944-a355-84c8-4c8f-f4e9b389a41a@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).