From: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
To: Jonny Grant <jg@jguk.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Bug c/108224] [PATCH] add srandom random initstate setstate
Date: Mon, 26 Dec 2022 14:49:26 +0530 [thread overview]
Message-ID: <CAAgBjMmhAeFkQb8RUNg2g7=qX8wdVKArdsceyhhM3SN6ji7AUg@mail.gmail.com> (raw)
In-Reply-To: <881e795d-34c8-0445-74cf-cb68192d2dfe@jguk.org>
On Mon, 26 Dec 2022 at 14:25, Jonny Grant <jg@jguk.org> wrote:
>
>
>
> From 6ff344979af46dbcd739dd9068d6d595547e4c27 Mon Sep 17 00:00:00 2001
> From: Jonathan Grant <jg@jguk.org>
> Date: Sun, 25 Dec 2022 22:38:44 +0000
> Subject: [PATCH] add srandom random initstate setstate
>
> ---
> gcc/c-family/known-headers.cc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/gcc/c-family/known-headers.cc b/gcc/c-family/known-headers.cc
> index 9c256173b82..ade9fa2dcc0 100644
> --- a/gcc/c-family/known-headers.cc
> +++ b/gcc/c-family/known-headers.cc
> @@ -171,6 +171,10 @@ get_stdlib_header_for_name (const char *name, enum stdlib lib)
> {"getenv", {"<stdlib.h>", "<cstdlib>"} },
> {"malloc", {"<stdlib.h>", "<cstdlib>"} },
> {"realloc", {"<stdlib.h>", "<cstdlib>"} },
> + {"random", {"<stdlib.h>", "<cstdlib>"} },
> + {"srandom", {"<stdlib.h>", "<cstdlib>"} },
> + {"initstate", {"<stdlib.h>", "<cstdlib>"} },
> + {"setstate", {"<stdlib.h>", "<cstdlib>"} },
>
> /* <string.h> and <cstring>. */
> {"memchr", {"<string.h>", "<cstring>"} },
Hi Jonny,
Thanks for the patch. A couple of things:
(a) Could you please add a test-case for the above symbols ? See
testsuite/gcc.dg/missing-header-fixit-4.c
for a similar example for printf.
(b) The patch is missing changelog.
I assume you've tested the patch with bootstrap+regtest ?
Thanks,
Prathamesh
> --
> 2.37.2
next prev parent reply other threads:[~2022-12-26 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 8:55 Jonny Grant
2022-12-26 9:19 ` Prathamesh Kulkarni [this message]
2022-12-27 22:31 ` Jonny Grant
2023-01-01 7:42 ` Prathamesh Kulkarni
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='CAAgBjMmhAeFkQb8RUNg2g7=qX8wdVKArdsceyhhM3SN6ji7AUg@mail.gmail.com' \
--to=prathamesh.kulkarni@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jg@jguk.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).