public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 13 release -- 2022-10-01 update
Date: Mon, 10 Oct 2022 07:45:24 -0700	[thread overview]
Message-ID: <Y0QwBJIXUUgo75Q4@adacore.com> (raw)
In-Reply-To: <225620a3-5eb4-eeef-e0b7-86f18817216e@foss.st.com>

> > > 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.

OK; let's see what happens with the FSF assignment process.

It seems indeed desirable for us to include it in GDB 13, but I don't
think it will be blocking us if the patch gets delayed because
we're waiting for the assignment to come through (looking at progress
on the other issues, I think the FSF still has time). Worst case
scenario, if everything but this patch is done, we can start by
branching and creating our first pre-release. I think it'll be
relatively easy and safe to backport once the patch is approved.

Just for the avoidance of doubt, I assume you guys are finalizing
the patch in parallel to waiting for the FSF to get back to us,
right? Ideally, as soon as we have the paperwork done, the patch
gets pushed.

Thank you,
-- 
Joel

  reply	other threads:[~2022-10-10 14:45 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 [this message]
2022-10-10 18:39         ` Joel Brobecker
2022-10-26 14:30       ` Torbjorn SVENSSON
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=Y0QwBJIXUUgo75Q4@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=torbjorn.svensson@foss.st.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).