From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Cc: Martin Sebor <msebor@redhat.com>
Subject: [PATCH 0/2] vfprintf cleanups to avoid -Waddress warning
Date: Wed, 22 Sep 2021 09:09:50 +0200 [thread overview]
Message-ID: <cover.1632294469.git.fweimer@redhat.com> (raw)
These two patches slightly clean up stdio-common/vfprintf-internal.c,
reducing code duplication slightly and removing a GCC 12 warning.
Tested on i686-linux-gnu and x86_64-linux-gnu. Built with
build-many-glibcs.py.
Thanks,
Florian
Florian Weimer (2):
vfprintf: Handle floating-point cases outside of process_arg macro
vfprintf: Unify argument handling in process_arg
stdio-common/vfprintf-internal.c | 392 +++++++++++++------------------
1 file changed, 164 insertions(+), 228 deletions(-)
base-commit: 1356f38df5be0776823eb2c40cc4e607b86b9680
--
2.31.1
next reply other threads:[~2021-09-22 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 7:09 Florian Weimer [this message]
2021-09-22 7:10 ` [PATCH 1/2] vfprintf: Handle floating-point cases outside of process_arg macro Florian Weimer
2021-09-22 13:55 ` Andreas Schwab
2021-09-22 7:10 ` [PATCH 2/2] vfprintf: Unify argument handling in process_arg Florian Weimer
2021-09-22 14:17 ` Andreas Schwab
2021-09-23 10:07 ` Florian Weimer
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=cover.1632294469.git.fweimer@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=msebor@redhat.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).