public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/97680] [11 Regression] new test case c-c++-common/zero-scratch-regs-10.c in r11-4578 has excess errors
Date: Wed, 31 Mar 2021 06:58:14 +0000 [thread overview]
Message-ID: <bug-97680-4-pzqYwB2SK3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97680-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97680
--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:0989e99470c2a6797bacf6d04888bc9a46a632a8
commit r11-7922-g0989e99470c2a6797bacf6d04888bc9a46a632a8
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Mar 31 08:55:38 2021 +0200
testsuite: Disable zero-scratch-regs-{8, 9, 10, 11}.c on all but ...
[PR97680]
Seems the target hook is only defined on
config/i386/i386.c:#undef TARGET_ZERO_CALL_USED_REGS
config/i386/i386.c:#define TARGET_ZERO_CALL_USED_REGS
ix86_zero_call_used_regs
config/sparc/sparc.c:#undef TARGET_ZERO_CALL_USED_REGS
config/sparc/sparc.c:#define TARGET_ZERO_CALL_USED_REGS
sparc_zero_call_used_regs
but apparently many of the tests actually succeed on various targets that
don't define those hooks. E.g. I haven't seen them to fail on aarch64,
on arm only the -10.c fails, on powerpc*/s390* all {8,9,10,11} fail (plus
5 is skipped on power*-aix*).
On ia64 according to testresults {6,7,8,9,10,11} fail, some with ICEs.
On mipsel according to testresults {9,10,11} fail, some with ICEs.
On nvptx at least 1-9 succeed, 10-11 don't know, don't have assert.h
around.
I've kept {5,6,7} with aix,ia64,ia64 skipped because those seems like
outliers, it works pretty much everywhere but on those.
The rest have known good targets.
2021-03-31 Jakub Jelinek <jakub@redhat.com>
PR testsuite/97680
* c-c++-common/zero-scratch-regs-6.c: Skip on ia64.
* c-c++-common/zero-scratch-regs-7.c: Likewise.
* c-c++-common/zero-scratch-regs-8.c: Change from dg-skip-if of
selected unsupported triplets to all targets but selected triplets
of supported targets.
* c-c++-common/zero-scratch-regs-9.c: Likewise.
* c-c++-common/zero-scratch-regs-10.c: Likewise.
* c-c++-common/zero-scratch-regs-11.c: Likewise.
next prev parent reply other threads:[~2021-03-31 6:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 20:00 [Bug testsuite/97680] New: " seurer at gcc dot gnu.org
2020-11-02 20:12 ` [Bug testsuite/97680] " qinzhao at gcc dot gnu.org
2020-11-03 7:22 ` [Bug testsuite/97680] [11 Regression] " rguenth at gcc dot gnu.org
2020-11-03 14:32 ` qinzhao at gcc dot gnu.org
2020-11-04 13:26 ` rsandifo at gcc dot gnu.org
2020-11-07 16:43 ` iains at gcc dot gnu.org
2020-11-08 9:44 ` iains at gcc dot gnu.org
2021-01-14 9:32 ` rguenth at gcc dot gnu.org
2021-02-23 12:27 ` rguenth at gcc dot gnu.org
2021-02-26 12:17 ` rguenth at gcc dot gnu.org
2021-02-26 12:17 ` rguenth at gcc dot gnu.org
2021-02-26 16:18 ` qing.zhao at oracle dot com
2021-03-18 14:26 ` cvs-commit at gcc dot gnu.org
2021-03-18 16:17 ` jakub at gcc dot gnu.org
2021-03-18 17:49 ` clyon at gcc dot gnu.org
2021-03-31 6:58 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-31 7:03 ` [Bug testsuite/97680] [12 " jakub at gcc dot gnu.org
2022-05-06 8:30 ` [Bug testsuite/97680] [12/13 " jakub at gcc dot gnu.org
2023-05-08 12:21 ` [Bug testsuite/97680] [12/13/14 " rguenth at gcc dot gnu.org
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=bug-97680-4-pzqYwB2SK3@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).