public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-10021] [testsuite] [analyzer] require fork where used
Date: Thu, 18 Apr 2024 11:15:11 +0000 (GMT)	[thread overview]
Message-ID: <20240418111511.B19433858C53@sourceware.org> (raw)

https://gcc.gnu.org/g:8a1170903212ed31fd970d3c1b9fabf50868d01a

commit r14-10021-g8a1170903212ed31fd970d3c1b9fabf50868d01a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Apr 18 08:01:15 2024 -0300

    [testsuite] [analyzer] require fork where used
    
    Mark tests that fail due to the lack of fork, as in vxworks kernel
    mode, as requiring fork.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/analyzer/pipe-glibc.c: Require fork.
            * gcc.dg/analyzer/pipe-manpages.c: Likewise.

Diff:
---
 gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c    | 5 +++--
 gcc/testsuite/gcc.dg/analyzer/pipe-manpages.c | 2 ++
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c b/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c
index 60558a870b9..fe38ddef395 100644
--- a/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c
+++ b/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c
@@ -1,6 +1,7 @@
-/* Example of pipe usage from glibc manual.  */
-
 /* { dg-skip-if "" { "avr-*-*" } } */
+/* { dg-require-fork "" } */
+
+/* Example of pipe usage from glibc manual.  */
 
 #include <sys/types.h>
 #include <unistd.h>
diff --git a/gcc/testsuite/gcc.dg/analyzer/pipe-manpages.c b/gcc/testsuite/gcc.dg/analyzer/pipe-manpages.c
index 6b9ae4d2602..ac5805fdba0 100644
--- a/gcc/testsuite/gcc.dg/analyzer/pipe-manpages.c
+++ b/gcc/testsuite/gcc.dg/analyzer/pipe-manpages.c
@@ -1,3 +1,5 @@
+/* { dg-require-fork "" } */
+
 /* Example of "pipe" from release 5.13 of the Linux man-pages project.
 
 Copyright (C) 2005, 2008, Michael Kerrisk <mtk.manpages@gmail.com>

                 reply	other threads:[~2024-04-18 11:15 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=20240418111511.B19433858C53@sourceware.org \
    --to=aoliva@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).