From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B78D03858024; Mon, 2 Nov 2020 20:12:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B78D03858024 From: "qinzhao at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/97680] new test case c-c++-common/zero-scratch-regs-10.c in r11-4578 has excess errors Date: Mon, 02 Nov 2020 20:12:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qinzhao at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 20:12:50 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97680 --- Comment #1 from qinzhao at gcc dot gnu.org --- (In reply to seurer from comment #0) > commit d10f3e900b0377b4760a090b0f90371bcef01686 > Author: qing zhao > Date: Fri Oct 30 20:41:38 2020 +0100 >=20 > If looks like the errors are all like this: >=20 > FAIL: c-c++-common/zero-scratch-regs-10.c -std=3Dgnu++98 (test for excess > errors) > Excess errors: > /home/seurer/gcc/git/gcc-test/gcc/testsuite/c-c++-common/zero-scratch-reg= s- > 10.c:77:1: sorry, unimplemented: '-fzero-call-used_regs' not supported on > this target Hi, this is an expected error on this platform since the middle-end implementation of -fzero-call-used-regs doesn't work for it. Please mark th= ese testing case as expected failure on this platform, or finish the implementa= tion on powerpc backend=