From: Jonathan Yong <10walls@gmail.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Cc: NightStrike <nightstrike@gmail.com>
Subject: [Patch] pr65658.c: fix excess warnings on LLP64 targets
Date: Sat, 28 Jan 2023 18:16:40 +0000 [thread overview]
Message-ID: <ab676a99-e22c-08fa-787a-4b7586a2bd60@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 73 bytes --]
Patch OK?
gcc/testsuite/ChangeLog:
* gcc.dg/pr65658.c: fix LLP64 test.
[-- Attachment #2: 0001-pr65658.c-fix-excess-warnings-on-LLP64-targets.patch --]
[-- Type: text/x-patch, Size: 1499 bytes --]
From bd2634e2795723f290dcf4bbb06e70fb6ca6af51 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10walls@gmail.com>
Date: Sat, 28 Jan 2023 18:12:50 +0000
Subject: [PATCH] pr65658.c: fix excess warnings on LLP64 targets
gcc/testsuite/ChangeLog:
* gcc.dg/pr65658.c: fix LLP64 test.
Signed-off-by: Jonathan Yong <10walls@gmail.com>
---
gcc/testsuite/gcc.dg/pr65658.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/gcc/testsuite/gcc.dg/pr65658.c b/gcc/testsuite/gcc.dg/pr65658.c
index bb5c37adbe3..4847dc2d5c7 100644
--- a/gcc/testsuite/gcc.dg/pr65658.c
+++ b/gcc/testsuite/gcc.dg/pr65658.c
@@ -16,10 +16,10 @@ struct undeffoo
};
struct problem
{
- unsigned long l1;
- unsigned long l2;
- unsigned long l3;
- unsigned long l4;
+ __UINTPTR_TYPE__ l1;
+ __UINTPTR_TYPE__ l2;
+ __UINTPTR_TYPE__ l3;
+ __UINTPTR_TYPE__ l4;
};
static unsigned int undef1, undef2, undef3, undef4, undef5, undef6;
static void *undefvp1;
@@ -37,7 +37,7 @@ undefinit1 (void)
}
static int
-undefinit2 (void *problemp, unsigned long problem)
+undefinit2 (void *problemp, __UINTPTR_TYPE__ problem)
{
int ret, u;
if (undefinit1 ())
@@ -60,7 +60,7 @@ fn6 (struct undefinfo *uip, struct problem *problem)
unsigned long amt;
if (external_function3 (((void *) 0), ((void *) 0), &amt, 0, 0))
return 1;
- problem->l1 = (unsigned long) undefvp1;
+ problem->l1 = (__UINTPTR_TYPE__) undefvp1;
problem->l4 = uip->l1;
problem->l3 = uip->l2;
return 0;
--
2.39.1
next reply other threads:[~2023-01-28 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 18:16 Jonathan Yong [this message]
2023-02-09 3:17 ` NightStrike
2023-02-13 7:04 ` Jeff Law
2023-02-13 11:50 ` Jonathan Yong
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=ab676a99-e22c-08fa-787a-4b7586a2bd60@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@gmail.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).