From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 34CC13858291 for ; Thu, 12 Jan 2023 21:04:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 34CC13858291 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1673557443; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=VYqjB/NvXNidihHsTmwoNNe+xyIwsgY4zok+nvvlSvY=; b=T6mbhur9W1A5fJ80BoIwKQhcHM/NmMonqEcO2xsYtuI1YxDiRbLmaOgmBIIyWHU+fgzrtj /csuF2KM14flcvSrLi7vLUiYe3YtpqQGGrgWmfHyWMFipM7ZYummgqFa/33RaY78p3zE+s fhqSEkI/niuJ6cFLAJvERtVv7gq0gA4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-310-VhJojE-8PACLjRAHOCrexw-1; Thu, 12 Jan 2023 16:04:02 -0500 X-MC-Unique: VhJojE-8PACLjRAHOCrexw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 6946E803525; Thu, 12 Jan 2023 21:04:02 +0000 (UTC) Received: from localhost (unknown [10.33.36.192]) by smtp.corp.redhat.com (Postfix) with ESMTP id 32C6840C2064; Thu, 12 Jan 2023 21:04:02 +0000 (UTC) From: Jonathan Wakely To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: [PATCH] libstdc++: Make forward to C version if included by C Date: Thu, 12 Jan 2023 21:04:01 +0000 Message-Id: <20230112210401.932343-1-jwakely@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-11.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,GIT_PATCH_0,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: I was asked about this privately. I don't really like that it would ever be needed, but it also seems fairly harmless. We already do similar things for some of the libstdc++ versions of etc. Any objections? Tested x86_64-linux. -- >8 -- This shouldn't be needed, but apparently the Bazel build tool has a misfeature where it uses -nostdinc and explicitly provides the system include paths, and it uses the same set of paths for compiling C and C++ code. This means that the libstdc++ header paths get used when compiling C code, and so our new gets included. Just forward to the C header using #include_next if that happens. libstdc++-v3/ChangeLog: * include/c_compatibility/stdatomic.h: Use #include_next if included by C code. --- libstdc++-v3/include/c_compatibility/stdatomic.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libstdc++-v3/include/c_compatibility/stdatomic.h b/libstdc++-v3/include/c_compatibility/stdatomic.h index a51a84c2054..aa7bbb923dc 100644 --- a/libstdc++-v3/include/c_compatibility/stdatomic.h +++ b/libstdc++-v3/include/c_compatibility/stdatomic.h @@ -124,7 +124,7 @@ using std::atomic_flag_clear_explicit; using std::atomic_thread_fence; using std::atomic_signal_fence; -#elif defined __clang__ +#elif !defined __cplusplus || defined __clang__ # include_next #endif // C++23 #endif // _GLIBCXX_STDATOMIC_H -- 2.39.0