From: Thomas Schwinge <thomas@codesourcery.com>
To: Tom de Vries <Tom_deVries@mentor.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [testsuite] Add missing dg-require-effective-target alloca to gcc testsuite
Date: Tue, 28 Mar 2017 08:51:00 -0000 [thread overview]
Message-ID: <87zig5g68a.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <6e0d0f16-6db5-0369-f0dd-90344f5d272e@mentor.com>
Hi!
On Thu, 23 Mar 2017 16:46:19 +0100, Tom de Vries <Tom_deVries@mentor.com> wrote:
> I've run the gcc testsuite for target nvptx-none and ran into "test for
> excess errors" FAILs due to:
> ...
> sorry, unimplemented: target cannot support alloca.
> ...
>
> This patch marks those testcases as requiring alloca.
I observed that this test case:
> --- gcc/testsuite/gcc.dg/torture/pr71881.c (revision 246278)
> +++ gcc/testsuite/gcc.dg/torture/pr71881.c (working copy)
> @@ -1,4 +1,5 @@
> /* { dg-do compile } */
> +/* { dg-require-effective-target alloca } */
> /* { dg-additional-options "-g" } */
... as well as this test case:
> --- gcc/testsuite/gcc.c-torture/compile/pr79413.c (revision 246278)
> +++ gcc/testsuite/gcc.c-torture/compile/pr79413.c (working copy)
> @@ -1,3 +1,4 @@
> +/* { dg-require-effective-target alloca } */
> /* PR c/79413 */
... previously did PASS for anything but "-O0" (that is, any "alloca"
usage got optimized away). Now changed as follows:
[-FAIL:-]{+UNSUPPORTED:+} gcc.c-torture/compile/pr79413.c -O0 [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.c-torture/compile/pr79413.c -O1 [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.c-torture/compile/pr79413.c -O2 [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.c-torture/compile/pr79413.c -O3 -g [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.c-torture/compile/pr79413.c -Os [-(test for excess errors)-]
[-FAIL:-]{+UNSUPPORTED:+} gcc.dg/torture/pr71881.c -O0 [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.dg/torture/pr71881.c -O1 [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.dg/torture/pr71881.c -O2 [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.dg/torture/pr71881.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.dg/torture/pr71881.c -O3 -g [-(test for excess errors)-]
[-PASS:-]{+UNSUPPORTED:+} gcc.dg/torture/pr71881.c -Os [-(test for excess errors)-]
Would it be useful to XFAIL these for "-O0" only (along with a comment),
so that we continue testing that any "alloca" usage gets optimized away?
(Just an idea.)
Grüße
Thomas
next prev parent reply other threads:[~2017-03-28 8:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 15:46 Tom de Vries
2017-03-23 16:24 ` Thomas Schwinge
2017-03-23 16:51 ` Tom de Vries
2017-03-23 17:45 ` Mike Stump
2017-03-24 7:46 ` Tom de Vries
2017-03-24 12:43 ` Rainer Orth
2017-03-24 12:44 ` Richard Biener
2017-03-24 12:53 ` Rainer Orth
2017-03-24 13:04 ` Rainer Orth
2017-03-24 17:45 ` Mike Stump
2017-03-27 14:14 ` Tom de Vries
[not found] ` <d453445e-54be-d3b5-cc27-d73bdbcc855d@mentor.com>
2017-04-26 12:40 ` Tom de Vries
2017-04-26 12:50 ` Jakub Jelinek
2017-04-27 9:03 ` Tom de Vries
2017-04-28 8:23 ` Tom de Vries
2017-04-28 14:31 ` Tom de Vries
2017-04-28 1:35 ` Tom de Vries
2017-04-28 16:28 ` Jeff Law
2017-03-27 13:11 ` Tom de Vries
2017-03-28 8:51 ` Thomas Schwinge [this message]
2017-03-28 8:57 ` Tom de Vries
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=87zig5g68a.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@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).