From: Simon Marchi <simon.marchi@polymtl.ca>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: start of the GDB 11 release cycle
Date: Mon, 10 May 2021 11:10:32 -0400 [thread overview]
Message-ID: <5e6cc3b5-0e43-24b0-3b9b-d2c5076a31ea@polymtl.ca> (raw)
In-Reply-To: <AM8PR10MB4708FABC983142C8A63426ADE4549@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM>
On 2021-05-10 1:52 a.m., Bernd Edlinger wrote:
> I think my patch to improve the debug experience of optimized code
> is stable since january and might also be a good candidiate:
>
> [PATCH 0/4] Improve debugging of optimized code
> https://sourceware.org/pipermail/gdb-patches/2021-January/175617.html
I agree, however it's a matter of determining who is most qualified to
review this, it's not easy. I don't think I'm the best person for
this.
Simon
next prev parent reply other threads:[~2021-05-10 15:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 0:04 Joel Brobecker
2021-05-10 3:20 ` Mike Frysinger
2021-05-10 22:10 ` Joel Brobecker
2021-05-24 19:40 ` Joel Brobecker
2021-05-25 2:01 ` Mike Frysinger
2021-05-26 22:03 ` Joel Brobecker
2021-05-29 15:58 ` Mike Frysinger
2021-05-10 3:52 ` Luis Machado
2021-05-10 22:11 ` Joel Brobecker
2021-05-11 11:05 ` Luis Machado
2021-05-11 17:00 ` Joel Brobecker
2021-05-12 18:15 ` Luis Machado
2021-05-24 19:42 ` Joel Brobecker
2021-05-24 20:27 ` Luis Machado
2021-05-24 21:02 ` Joel Brobecker
2021-05-25 10:46 ` Luis Machado
2021-05-26 22:04 ` Joel Brobecker
2021-05-10 5:52 ` Bernd Edlinger
2021-05-10 15:10 ` Simon Marchi [this message]
2021-05-10 16:07 ` Andrew Burgess
2021-05-10 16:57 ` Simon Marchi
2021-05-10 22:12 ` Joel Brobecker
2021-05-11 12:45 ` Rainer Orth
2021-05-11 16:57 ` 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=5e6cc3b5-0e43-24b0-3b9b-d2c5076a31ea@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=bernd.edlinger@hotmail.de \
--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).