From: NightStrike <nightstrike@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed] testsuite: Add testcases from PR108292 and PR108308
Date: Wed, 11 Jan 2023 07:22:50 -0500 [thread overview]
Message-ID: <CAF1jjLuJCt7FB6ioD1uH2cSQX-D7njYh4e1prh_yhpfBe7eytQ@mail.gmail.com> (raw)
In-Reply-To: <Y76oJT6vXmEhQMDB@tucnak>
On Wed, Jan 11, 2023 at 7:14 AM Jakub Jelinek <jakub@redhat.com> wrote:
> I've committed following after regtesting it on x86_64-linux and i686-linux:
...
> +/* { dg-do run { target int32 } } */
Ah, I didn't realize you meant literally int32. I didn't see that as
a choice here:
https://gcc.gnu.org/onlinedocs/gccint/Effective-Target-Keywords.html
Is that a case of missing documentation?
prev parent reply other threads:[~2023-01-11 12:23 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
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 [this message]
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=CAF1jjLuJCt7FB6ioD1uH2cSQX-D7njYh4e1prh_yhpfBe7eytQ@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).