From: Jonathan Yong <10walls@gmail.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: [Patch] gcc.c-torture/compile/103818.c: enable for llp64 too
Date: Sun, 26 Feb 2023 06:38:58 +0000 [thread overview]
Message-ID: <f4ec9808-7f52-659f-7859-72573bb76263@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 92 bytes --]
Patch OK for master branch? I did not see any obvious issues to exclude
LLP64 specifically.
[-- Attachment #2: 0001-gcc.c-torture-compile-103818.c-enable-for-llp64-too.patch --]
[-- Type: text/x-patch, Size: 859 bytes --]
From 9c770936c4c6ffb59d15e5c1ce331494ba102250 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10walls@gmail.com>
Date: Sun, 26 Feb 2023 06:34:04 +0000
Subject: [PATCH] gcc.c-torture/compile/103818.c: enable for llp64 too
gcc/testsuite/ChangeLog:
* gcc.c-torture/compile/103818.c: enable test for llp64.
Signed-off-by: Jonathan Yong <10walls@gmail.com>
---
gcc/testsuite/gcc.c-torture/compile/103818.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/gcc.c-torture/compile/103818.c b/gcc/testsuite/gcc.c-torture/compile/103818.c
index e6cbe7860cf..63090534f4c 100644
--- a/gcc/testsuite/gcc.c-torture/compile/103818.c
+++ b/gcc/testsuite/gcc.c-torture/compile/103818.c
@@ -1,4 +1,4 @@
-/* { dg-do compile { target lp64 } } */
+/* { dg-do compile { target { lp64 || lp64 } } } */
struct A { int b[1]; };
void
--
2.39.2
next reply other threads:[~2023-02-26 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 6:38 Jonathan Yong [this message]
2023-02-28 2:10 ` Hans-Peter Nilsson
2023-02-28 7:23 ` Jonathan Yong
2023-03-11 16:18 ` Jeff Law
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=f4ec9808-7f52-659f-7859-72573bb76263@gmail.com \
--to=10walls@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).