From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: GDB 13 release -- 2022-10-01 update
Date: Wed, 26 Oct 2022 16:30:07 +0200 [thread overview]
Message-ID: <2f378fd5-6f2d-0bea-9a1f-ecdf9361316c@foss.st.com> (raw)
In-Reply-To: <225620a3-5eb4-eeef-e0b7-86f18817216e@foss.st.com>
On 2022-10-10 09:40, Torbjorn SVENSSON wrote:
> Hi Joel,
>
> On 2022-10-10 01:55, Joel Brobecker wrote:
>> Hello Torbjorn,
>>
>>> I would like to land 2 patches for Cortex-M before the release.
>>>
>>> * https://sourceware.org/bugzilla/show_bug.cgi?id=28549
>>
>> Can you provide more information about this one?
>>
>> - What's the motivation behind suggesting this PR? This will be
>> important for us to know should resolution of this PR be delayed.
>
> The motivation is simply that with the last improvements on the stack
> unwind on Cortex-M, the stack unwind can take a considerable amount of
> time (endless?) if the CPU is in lockup state.
>
>> - Have the latest version of the patches been submitted for review?
>> If yes, can you provide URLs? In reading the PR, I am not really
>> sure how many patches we are talking about, and where those patches
>> migth be residing.
>
> I think Luis has the most up to date status here. Thomaz has created a
> single patch (https://sourceware.org/bugzilla/attachment.cgi?id=13853)
> that would handle the problematic case, but as there is no copyright on
> file for Tomaz, he needed to send one to FSF. A few weeks back, Thomaz
> did just that, but there has been no response from FSF.
> The patch is in a sort-of-working state. There are some minor things to
> be addressed, but before the patch can be shared on the ML, the
> copyright pat must be handled.
>
>>
>> Thank you.
>>
With the merges today (thank you Luis for those!), I no longer have any
item for the GDB 13 release.
I would say that it would be nice to have the sN <--> dM pseudo register
sync fixed, but I fear that it's a bigger topic and that the time left
until the release is not enough to get it into a mergeable state.
Kind regards,
Torbjörn
next prev parent reply other threads:[~2022-10-26 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 0:12 Joel Brobecker
2022-10-02 7:23 ` Torbjorn SVENSSON
2022-10-09 23:55 ` Joel Brobecker
2022-10-10 7:40 ` Torbjorn SVENSSON
2022-10-10 14:45 ` Joel Brobecker
2022-10-10 18:39 ` Joel Brobecker
2022-10-26 14:30 ` Torbjorn SVENSSON [this message]
2022-10-26 14:54 ` Joel Brobecker
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=2f378fd5-6f2d-0bea-9a1f-ecdf9361316c@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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).