From: Ammar Faizi <[email protected]>
To: "Paul E. McKenney" <[email protected]>, Willy Tarreau <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Facebook Kernel Team <[email protected]>
Subject: [PATCH v1 0/2] nolibc updates for Linux 5.20
Date: Fri, 20 May 2022 00:21:14 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Willy,
Hi Paul,
Not much to do this time. Only small nolibc updates here. There are two
patches in this series.
1. Address Willy's comment about overflow checking in the multiplication
operation [1]. This patch supports overflow checking for older
compiler versions. Currently, we use `__builtin_mul_overflow()` that
doesn't exist in older compiler versions. Instead of using this
built-in, use a simple division to check for overflow in the `calloc()`
function.
2. The compiler can warn us about wrong `printf` arguments. This patch
enables the warnings. Currently, only two functions use this attribute:
`printf` and `fprintf`.
Hopefully, I can send more updates for 5.21+.
Thank you!
Link: https://lore.kernel.org/lkml/[email protected] [1]
Signed-off-by: Alviro Iskandar Setiawan <[email protected]>
Signed-off-by: Ammar Faizi <[email protected]>
---
Alviro Iskandar Setiawan (1):
tools/nolibc/stdio: Add format attribute to enable printf warnings
Ammar Faizi (1):
tools/nolibc/stdlib: Support overflow checking for older compiler versions
tools/include/nolibc/stdio.h | 4 ++--
tools/include/nolibc/stdlib.h | 7 +++----
2 files changed, 5 insertions(+), 6 deletions(-)
base-commit: 9a9e459ed0e76710f1258b6c1d4c0316b52b4b08
prerequisite-patch-id: e4a9acdc12961f2d4c6bb99e4790b8ffa9d15174
prerequisite-patch-id: 5a618e6a72c7d2beef4ba2c2cf01dadfbaf9a996
prerequisite-patch-id: 1bcffd448f6984eee80d86560af19672cd4ae716
prerequisite-patch-id: 3e31c80bd4dd532e30b4bba76e5d98647e21184b
prerequisite-patch-id: 34e531967a67791d5b3c3e071527de7235715906
prerequisite-patch-id: 14105c6ae9dcc068ddf12a7c1bf431066199b813
prerequisite-patch-id: 4299173943ea579f538da00488fb1a7b1a690a79
prerequisite-patch-id: dd85164f2ec9eb8cea64ab801abac614f9d0c8f5
prerequisite-patch-id: 2c1b940635d1564e26b9959eb57cf9fa6983cb2f
--
Ammar Faizi
next reply other threads:[~2022-05-19 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 17:21 Ammar Faizi [this message]
2022-05-19 17:21 ` [PATCH v1 1/2] tools/nolibc/stdlib: Support overflow checking for older compiler versions Ammar Faizi
2022-05-20 4:19 ` Willy Tarreau
2022-05-20 11:29 ` Alviro Iskandar Setiawan
2022-05-20 17:32 ` Paul E. McKenney
2022-05-19 17:21 ` [PATCH v1 2/2] tools/nolibc/stdio: Add format attribute to enable printf warnings Ammar Faizi
2022-05-20 4:21 ` Willy Tarreau
2022-05-20 4:23 ` [PATCH v1 0/2] nolibc updates for Linux 5.20 Willy Tarreau
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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