From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Stephen Kitt <steve@sk2.org>, Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 9/9] malloc_info.3: Use intptr_t to store pointers
Date: Sat, 8 Jan 2022 03:25:20 +0100 [thread overview]
Message-ID: <b4622fe8-ec81-654f-fa32-bf2efa0459ea@gmail.com> (raw)
In-Reply-To: <20220107164621.275794-9-steve@sk2.org>
Hi Stephen,
On 1/7/22 17:46, Stephen Kitt wrote:
> int isn't large enough to store pointers on all platforms, use
> intptr_t instead.
Well, since the pointer came from a previous 'int', there should be no
problem. But since the C language (or even POSIX) is very permissive
about what a conforming implementation can do with pointers, and it only
guarantees conversions to/from [u]intptr_t, I'd take this patch for
correctness. However...
I still don't like at all the fact that compilers require an explicit
cast. Casts are dangerous. Period. I haven't seen a place where casts
are good, except when you explicitly want to rely on undefined behavior
(which I've found very useful in a few cases). It should be clear to
the compiler that we're doing the right thing, since we declared the
variable to be 'intptr_t', which is by itself very rare. Requiring a
cast adds no clarity, while it does increase the chances of a bug.
I'd like to know your opinion. I think I'll remove the cast, even if
compilers are going to give a warning for implicitly converting from
pointer to integer (intptr_t). I'd say patch the compiler, not the code.
Thanks,
Alex
>
> Signed-off-by: Stephen Kitt <steve@sk2.org>
> ---
> man3/malloc_info.3 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man3/malloc_info.3 b/man3/malloc_info.3
> index a5b8d34f9..3baa891fd 100644
> --- a/man3/malloc_info.3
> +++ b/man3/malloc_info.3
> @@ -198,7 +198,7 @@ static int numThreads, numBlocks;
> static void *
> thread_func(void *arg)
> {
> - int tn = (int) arg;
> + intptr_t tn = (intptr_t) arg;
>
> /* The multiplier \(aq(2 + tn)\(aq ensures that each thread (including
> the main thread) allocates a different amount of memory. */
> @@ -237,7 +237,7 @@ main(int argc, char *argv[])
>
> /* Create threads that allocate different amounts of memory. */
>
> - for (int tn = 0; tn < numThreads; tn++) {
> + for (intptr_t tn = 0; tn < numThreads; tn++) {
> errno = pthread_create(&thr[tn], NULL, thread_func,
> (void *) tn);
> if (errno != 0)
--
Alejandro Colomar
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-01-08 2:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 16:46 [PATCH 1/9] Add a target to check example programs Stephen Kitt
2022-01-07 16:46 ` [PATCH 2/9] seccomp.2: Use syscall() in the example code Stephen Kitt
2022-01-08 1:18 ` Alejandro Colomar (man-pages)
2022-01-07 16:46 ` [PATCH 3/9] inet.3: Switch to _DEFAULT_SOURCE in the example Stephen Kitt
2022-01-08 1:26 ` Alejandro Colomar (man-pages)
2022-01-08 9:06 ` Stephen Kitt
2022-01-07 16:46 ` [PATCH 4/9] matherr.3: Exclude the example from analysis Stephen Kitt
2022-01-08 1:31 ` Alejandro Colomar (man-pages)
2022-01-08 9:12 ` Stephen Kitt
2022-01-07 16:46 ` [PATCH 5/9] mq_notify.3: Add signal.h for SIGEV_THREAD Stephen Kitt
2022-01-08 1:38 ` Alejandro Colomar (man-pages)
2022-01-07 16:46 ` [PATCH 6/9] newlocale.3: Use LC_GLOBAL_LOCALE, not ..._HANDLE Stephen Kitt
2022-01-08 1:41 ` Alejandro Colomar (man-pages)
2022-01-08 9:13 ` Jakub Wilk
2022-01-08 17:58 ` Alejandro Colomar (man-pages)
2022-01-07 16:46 ` [PATCH 7/9] pkeys.7: Update the example to match glibc Stephen Kitt
2022-01-08 1:59 ` Alejandro Colomar (man-pages)
2022-01-08 14:18 ` Stephen Kitt
2022-01-08 19:20 ` Alejandro Colomar (man-pages)
2022-01-07 16:46 ` [PATCH 8/9] strtok.3: Enable example analysis, fix declaration Stephen Kitt
2022-01-08 2:04 ` Alejandro Colomar (man-pages)
2022-01-07 16:46 ` [PATCH 9/9] malloc_info.3: Use intptr_t to store pointers Stephen Kitt
2022-01-08 2:25 ` Alejandro Colomar (man-pages) [this message]
2022-01-08 10:30 ` Jakub Wilk
2022-01-08 17:09 ` Stephen Kitt
2022-01-08 19:17 ` Alejandro Colomar (man-pages)
2022-01-08 1:15 ` [PATCH 1/9] Add a target to check example programs Alejandro Colomar (man-pages)
2022-01-08 9:22 ` Stephen Kitt
2022-01-08 19:05 ` Alejandro Colomar (man-pages)
2022-01-08 19:38 ` Alejandro Colomar (man-pages)
2022-01-08 2:02 ` Alejandro Colomar (man-pages)
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=b4622fe8-ec81-654f-fa32-bf2efa0459ea@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=steve@sk2.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