public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6374] testsuite/108942 - use sizetype in GIMPLE FE testcase Date: Tue, 28 Feb 2023 10:37:22 +0000 (GMT) [thread overview] Message-ID: <20230228103722.82EEF3858D33@sourceware.org> (raw) https://gcc.gnu.org/g:41c02eeb309b3be58683be8f9961f3894b6fb4c7 commit r13-6374-g41c02eeb309b3be58683be8f9961f3894b6fb4c7 Author: Richard Biener <rguenther@suse.de> Date: Tue Feb 28 11:36:01 2023 +0100 testsuite/108942 - use sizetype in GIMPLE FE testcase The following properly uses __SIZETYPE__ for pointer offsets. PR testsuite/108942 * gcc.dg/torture/ssa-fre-7.c: Use __SIZETYPE__. Diff: --- gcc/testsuite/gcc.dg/torture/ssa-fre-7.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/gcc.dg/torture/ssa-fre-7.c b/gcc/testsuite/gcc.dg/torture/ssa-fre-7.c index c9259b4ddaa..daf770a45c9 100644 --- a/gcc/testsuite/gcc.dg/torture/ssa-fre-7.c +++ b/gcc/testsuite/gcc.dg/torture/ssa-fre-7.c @@ -11,8 +11,8 @@ foo (int c) int * p; int i; int x[4]; - long unsigned int _1; - long unsigned int _2; + __SIZETYPE__ _1; + __SIZETYPE__ _2; int _7; v4si _6;
reply other threads:[~2023-02-28 10:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230228103722.82EEF3858D33@sourceware.org \ --to=rguenth@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).