public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom de Vries <vries@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-7192] [testsuite] Require non_strict_prototype in a few tests
Date: Fri, 11 Feb 2022 07:46:30 +0000 (GMT)	[thread overview]
Message-ID: <20220211074630.51B5D385843F@sourceware.org> (raw)

https://gcc.gnu.org/g:7cc6a8d00af8a2ca8303a2894286911b8898da83

commit r12-7192-g7cc6a8d00af8a2ca8303a2894286911b8898da83
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Feb 9 16:48:27 2022 +0100

    [testsuite] Require non_strict_prototype in a few tests
    
    Require effective target non_strict_prototype in a few test-cases.
    
    Tested on nvptx.
    
    gcc/testsuite/ChangeLog:
    
    2022-02-10  Tom de Vries  <tdevries@suse.de>
    
            * gcc.c-torture/compile/pr100576.c: Require effective target
            non_strict_prototype.
            * gcc.c-torture/compile/pr97576.c: Same.

Diff:
---
 gcc/testsuite/gcc.c-torture/compile/pr100576.c | 2 ++
 gcc/testsuite/gcc.c-torture/compile/pr97576.c  | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/gcc/testsuite/gcc.c-torture/compile/pr100576.c b/gcc/testsuite/gcc.c-torture/compile/pr100576.c
index f2f40ec4512..f16a8224c6e 100644
--- a/gcc/testsuite/gcc.c-torture/compile/pr100576.c
+++ b/gcc/testsuite/gcc.c-torture/compile/pr100576.c
@@ -1,3 +1,5 @@
+/* { dg-require-effective-target non_strict_prototype } */
+
 /* PR middle-end/100576 */
 
 const char v[] = {0x12};
diff --git a/gcc/testsuite/gcc.c-torture/compile/pr97576.c b/gcc/testsuite/gcc.c-torture/compile/pr97576.c
index 28294c8597a..d2816132cc0 100644
--- a/gcc/testsuite/gcc.c-torture/compile/pr97576.c
+++ b/gcc/testsuite/gcc.c-torture/compile/pr97576.c
@@ -1,3 +1,5 @@
+/* { dg-require-effective-target non_strict_prototype } */
+
 void
 pc (void);


                 reply	other threads:[~2022-02-11  7:46 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=20220211074630.51B5D385843F@sourceware.org \
    --to=vries@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: 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).