From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: Mike Stump <mikestump@comcast.net>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [testsuite] Add missing dg-require-effective-target alloca to gcc testsuite
Date: Fri, 24 Mar 2017 12:43:00 -0000 [thread overview]
Message-ID: <yddy3vuc0j8.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <336349f0-b973-77c0-c5f5-710240312270@mentor.com> (Tom de Vries's message of "Fri, 24 Mar 2017 07:34:32 +0100")
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
Hi Tom,
> On 23/03/17 18:25, Mike Stump wrote:
>> On Mar 23, 2017, at 8:46 AM, 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.
>>
>> We'd encourage ports to support alloca. :-)
>>
>>> OK for trunk for stage1?
>>
>> Ok. Ok for release branches and trunk as well, if you want. I'd
>> recommend trunk, if your port is meant to work and test out nicely in gcc
>> 7.
>>
>
> Committed to trunk.
seems you didn't properly test this patchset. It caused
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++11 (test for warnings,
line 24)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++11 (test for warnings,
line 34)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++11 (test for excess err
ors)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++14 (test for warnings,
line 24)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++14 (test for warnings,
line 34)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++14 (test for excess err
ors)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++98 (test for warnings,
line 24)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++98 (test for warnings,
line 34)
+FAIL: c-c++-common/Wimplicit-fallthrough-7.c -std=gnu++98 (test for excess err
ors)
everywhere. Adding that dg-require-effective-target line requires
adjusting dg-warning etc. line numbers.
Fixed as follows, installed on mainline after checking with the
appropriate runtest invocations (for c and c++) on x86_64-pc-linux-gnu.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
2017-03-24 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
* c-c++-common/Wimplicit-fallthrough-7.c: Adjust dg-warning line
numbers.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: testsuite-Wimplicit-fallthrough-7.patch --]
[-- Type: text/x-patch, Size: 1273 bytes --]
# HG changeset patch
# Parent 288df338f490e514591c89d11734d7de56f62460
Adjust c-c++-common/Wimplicit-fallthrough-7.c line numbers
diff --git a/gcc/testsuite/c-c++-common/Wimplicit-fallthrough-7.c b/gcc/testsuite/c-c++-common/Wimplicit-fallthrough-7.c
--- a/gcc/testsuite/c-c++-common/Wimplicit-fallthrough-7.c
+++ b/gcc/testsuite/c-c++-common/Wimplicit-fallthrough-7.c
@@ -21,8 +21,8 @@ f (int i)
switch (i)
{
case 1:
- { /* { dg-warning "statement may fall through" "" { target c } 23 } */
- int a[i]; /* { dg-warning "statement may fall through" "" { target c++ } 24 } */
+ { /* { dg-warning "statement may fall through" "" { target c } 24 } */
+ int a[i]; /* { dg-warning "statement may fall through" "" { target c++ } 25 } */
}
case 2:
bar (99);
@@ -31,8 +31,8 @@ f (int i)
switch (i)
{
case 1:
- for (int j = 0; j < 10; j++) /* { dg-warning "statement may fall through" "" { target c } 33 } */
- map[j] = j; /* { dg-warning "statement may fall through" "" { target c++ } 34 } */
+ for (int j = 0; j < 10; j++) /* { dg-warning "statement may fall through" "" { target c } 34 } */
+ map[j] = j; /* { dg-warning "statement may fall through" "" { target c++ } 35 } */
case 2:
bar (99);
}
next prev parent reply other threads:[~2017-03-24 12:39 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 [this message]
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
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=yddy3vuc0j8.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).