From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Alan Modra <amodra@gmail.com>
Subject: [PATCH][pushed] libiberty: fix bad replacement.
Date: Tue, 10 May 2022 17:01:27 +0200 [thread overview]
Message-ID: <e1be1620-d3fc-87f0-6af6-232b4ac1df87@suse.cz> (raw)
Pushed as obvious.
Martin
libiberty/ChangeLog:
* random.c: Remove 'define PTR'.
---
libiberty/random.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/libiberty/random.c b/libiberty/random.c
index be8819dd6b8..cd0b7399e73 100644
--- a/libiberty/random.c
+++ b/libiberty/random.c
@@ -68,12 +68,10 @@ control over the state of the random number generator.
#define LONG_MAX ((long)(ULONG_MAX >> 1)) /* 0x7FFFFFFF for 32-bits*/
#ifdef __STDC__
-# define void *void *
# ifndef NULL
# define NULL (void *) 0
# endif
#else
-# define void *char *
# ifndef NULL
# define NULL (void *) 0
# endif
--
2.36.0
reply other threads:[~2022-05-10 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e1be1620-d3fc-87f0-6af6-232b4ac1df87@suse.cz \
--to=mliska@suse.cz \
--cc=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.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).