From: Jakub Jelinek <jakub@redhat.com>
To: NightStrike <nightstrike@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed] testsuite: Add testcases from PR108292 and PR108308
Date: Wed, 11 Jan 2023 10:06:56 +0100 [thread overview]
Message-ID: <Y758MNTDfKbWcPUQ@tucnak> (raw)
In-Reply-To: <CAF1jjLvp7tOEuKm+BfZPbbQmWob=-boVQntbzY8J6txTX4pQng@mail.gmail.com>
On Wed, Jan 11, 2023 at 03:58:40AM -0500, NightStrike wrote:
> On Fri, Jan 6, 2023 at 4:56 AM Jakub Jelinek via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> > --- gcc/testsuite/gcc.dg/pr108308.c.jj 2023-01-06 10:43:45.793009294 +0100
> > +++ gcc/testsuite/gcc.dg/pr108308.c 2023-01-06 10:43:40.218090375 +0100
> > @@ -0,0 +1,39 @@
> > +/* PR target/108308 */
> > +/* { dg-do run { target { ilp32 || lp64 } } } */
>
> This test passes on Windows, and I don't see anything in the test that
> jumps out at me as being affected by storing pointers in longs. Is
> there something I'm missing about why this would be disabled on LLP64?
Maybe the test just needs int32, it didn't look important enough to me.
ilp32 || lp64 covers most of important targets.
Jakub
next prev parent reply other threads:[~2023-01-11 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 9:56 Jakub Jelinek
2023-01-11 8:58 ` NightStrike
2023-01-11 9:06 ` Jakub Jelinek [this message]
2023-01-11 9:27 ` NightStrike
2023-01-11 9:43 ` Jakub Jelinek
2023-01-11 10:10 ` NightStrike
2023-01-11 12:14 ` Jakub Jelinek
2023-01-11 12:22 ` NightStrike
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=Y758MNTDfKbWcPUQ@tucnak \
--to=jakub@redhat.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).