public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3257] Restore intent of data-sym-multi-pool test Date: Tue, 31 Aug 2021 15:10:10 +0000 (GMT) [thread overview] Message-ID: <20210831151010.D08EE3857C63@sourceware.org> (raw) https://gcc.gnu.org/g:18f0e57b9a2f1b108831fcfb25cbcc4e2de65e8e commit r12-3257-g18f0e57b9a2f1b108831fcfb25cbcc4e2de65e8e Author: Jeff Law <jlaw@localhost.localdomain> Date: Tue Aug 31 11:08:50 2021 -0400 Restore intent of data-sym-multi-pool test gcc/testsuite * gcc.target/mips/mips.exp: Add tree-vrp to mips_option_group. * gcc.target/mips/data-sym-multi-pool.c: Add -fno-tree-vrp. Diff: --- gcc/testsuite/gcc.target/mips/data-sym-multi-pool.c | 2 +- gcc/testsuite/gcc.target/mips/mips.exp | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.target/mips/data-sym-multi-pool.c b/gcc/testsuite/gcc.target/mips/data-sym-multi-pool.c index 1936f5bf27e..26a622a44c9 100644 --- a/gcc/testsuite/gcc.target/mips/data-sym-multi-pool.c +++ b/gcc/testsuite/gcc.target/mips/data-sym-multi-pool.c @@ -1,5 +1,5 @@ /* { dg-do compile } */ -/* { dg-options "-mips16 -mcode-readable=yes" } */ +/* { dg-options "-mips16 -mcode-readable=yes -fno-tree-vrp" } */ /* { dg-skip-if "per-function expected output" { *-*-* } { "-flto" } { "" } } */ /* This testcase generates multiple constant pools within a function body. */ diff --git a/gcc/testsuite/gcc.target/mips/mips.exp b/gcc/testsuite/gcc.target/mips/mips.exp index 580e7c0c8f9..d4d4b90d897 100644 --- a/gcc/testsuite/gcc.target/mips/mips.exp +++ b/gcc/testsuite/gcc.target/mips/mips.exp @@ -333,6 +333,7 @@ foreach option { schedule-insns2 split-wide-types tree-vectorize + tree-vrp unroll-all-loops unroll-loops ipa-ra
reply other threads:[~2021-08-31 15:10 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=20210831151010.D08EE3857C63@sourceware.org \ --to=law@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).