public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Yong <10walls@gmail.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] gcc.c-torture/compile/103818.c: enable for llp64 too
Date: Tue, 28 Feb 2023 07:23:28 +0000	[thread overview]
Message-ID: <b81f6b64-96cf-c5ec-1608-964021fb76b1@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2302272107230.10325@arjuna.pair.com>

[-- Attachment #1: Type: text/plain, Size: 493 bytes --]

On 2/28/23 02:10, Hans-Peter Nilsson wrote:
> On Sun, 26 Feb 2023, Jonathan Yong via Gcc-patches wrote:
> 
>> Patch OK for master branch? I did not see any obvious issues to exclude LLP64
>> specifically.
> 
> I see "lp64 || lp64" in that patch (which should preferably have
> been sent inline, as it's harder to quote an attached patch,
> QED).  Sending the wrong version?  Don't forget to test it.
> 
> brgds, H-P

Corrected, previous patch was manually applied from a corrupted patch file.

[-- Attachment #2: 0004-gcc.c-torture-compile-103818.c-enable-for-llp64-too.patch --]
[-- Type: text/x-patch, Size: 864 bytes --]

From 52b1209193260a624f90c3ca759a83b975c2e8e0 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10walls@gmail.com>
Date: Sun, 26 Feb 2023 06:34:04 +0000
Subject: [PATCH 4/7] 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..57f56b6c09d 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 || llp64 } } } */
 struct A { int b[1]; };
 
 void
-- 
2.39.2


  reply	other threads:[~2023-02-28  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26  6:38 Jonathan Yong
2023-02-28  2:10 ` Hans-Peter Nilsson
2023-02-28  7:23   ` Jonathan Yong [this message]
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=b81f6b64-96cf-c5ec-1608-964021fb76b1@gmail.com \
    --to=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@bitrange.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).