From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] [gdb/build] Two gdbsupport/warning.m4 updates
Date: Wed, 28 Oct 2026 11:41:08 +0100 [thread overview]
Message-ID: <20261028104110.1700720-1-tdevries@suse.de> (raw)
This series contains two patches. Both of them are follow-ups on commit
df3eb64a53c ("gdbsupport: re-format and sort warning flags").
The first fixes a minor oversight.
The second makes ordering constraints between warnings explicit.
Tom de Vries (2):
[gdb/build] Put warnings one per line
[gdb/build] Rework warnings order
gdb/configure | 57 +++++++++++++++++++++++++++++++++++++------
gdbserver/configure | 57 +++++++++++++++++++++++++++++++++++++------
gdbsupport/configure | 57 +++++++++++++++++++++++++++++++++++++------
gdbsupport/warning.m4 | 57 +++++++++++++++++++++++++++++++++++++------
4 files changed, 196 insertions(+), 32 deletions(-)
base-commit: 7a593bcacd21f1ae684ed49dc2f8e3ea558c7c64
--
2.51.0
next reply other threads:[~2026-10-28 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 10:41 Tom de Vries [this message]
2026-10-28 10:41 ` [PATCH 1/2] [gdb/build] Put warnings one per line Tom de Vries
2026-10-28 10:41 ` [PATCH 2/2] [gdb/build] Rework warnings order Tom de Vries
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=20261028104110.1700720-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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