public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r12-3862] libstdc++: Disable PCH for test that depends on a macro being defined
Date: Thu, 23 Sep 2021 15:08:47 +0000 (GMT)	[thread overview]
Message-ID: <20210923150847.121E4385843E@sourceware.org> (raw)

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

commit r12-3862-g8fa90926e08950cc00d0e22eace27402b9f9fa57
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Sep 22 14:11:54 2021 +0100

    libstdc++: Disable PCH for test that depends on a macro being defined
    
    This test tries to ensure that <system_error> can be included after
    defining _XOPEN_SOURCE=600, which doesn't test anything if that header
    is already included via the <bits/stdc++.h> PCH before the macro
    definition. Disable PCH so that it behaves as intended.
    
    Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/19_diagnostics/headers/system_error/93151.cc:
            Disable PCH.

Diff:
---
 libstdc++-v3/testsuite/19_diagnostics/headers/system_error/93151.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libstdc++-v3/testsuite/19_diagnostics/headers/system_error/93151.cc b/libstdc++-v3/testsuite/19_diagnostics/headers/system_error/93151.cc
index c54c9a3022d..6aca63d4db3 100644
--- a/libstdc++-v3/testsuite/19_diagnostics/headers/system_error/93151.cc
+++ b/libstdc++-v3/testsuite/19_diagnostics/headers/system_error/93151.cc
@@ -1,4 +1,5 @@
 // { dg-do compile { target c++11 } }
+// { dg-add-options no_pch }
 
 // Copyright (C) 2020-2021 Free Software Foundation, Inc.
 //


                 reply	other threads:[~2021-09-23 15:08 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=20210923150847.121E4385843E@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-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).