From: Tom Tromey <tom@tromey.com>
To: Enze Li via Gdb-patches <gdb-patches@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>, Enze Li <enze.li@hotmail.com>,
Simon Marchi <simark@simark.ca>, Sam James <sam@gentoo.org>
Subject: Re: [PATCHv2] gdb: Ignore some stringop-overflow and restrict warnings on sparc
Date: Tue, 24 Jan 2023 08:19:38 -0700 [thread overview]
Message-ID: <87sfg0vu2d.fsf@tromey.com> (raw)
In-Reply-To: <OS3P286MB2152DDA9532274709FA16E66F0C99@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (Enze Li via Gdb-patches's message of "Tue, 24 Jan 2023 11:32:32 +0800")
>>>>> "Enze" == Enze Li via Gdb-patches <gdb-patches@sourceware.org> writes:
Enze> Since GDB 12, ChangeLog entries are no longer required. See here[1].
Enze> [1] https://sourceware.org/pipermail/gdb-patches/2021-June/179872.html
They might be for include/ since it's shared with gcc.
Can we even approve changes to include/diagnostics.h, or does it need to
go via gcc first? I don't really recall the status of this.
Tom
next prev parent reply other threads:[~2023-01-24 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 0:44 Mark Wielaard
2023-01-24 3:32 ` Enze Li
2023-01-24 9:35 ` Mark Wielaard
2023-01-24 15:25 ` Tom Tromey
2023-01-24 15:19 ` Tom Tromey [this message]
2023-01-24 15:22 ` Tom Tromey
2023-01-24 15:25 ` Tom Tromey
2023-01-24 19:26 ` Mark Wielaard
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=87sfg0vu2d.fsf@tromey.com \
--to=tom@tromey.com \
--cc=enze.li@hotmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=sam@gentoo.org \
--cc=simark@simark.ca \
/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).