From: Nathan Sidwell <nathan@acm.org>
Date: Tue, 21 Jun 2022 13:23:11 +0000 (-0700)
Subject: doc: Document module language-linkage supported
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f1fcd6e3ad911945bc3c24a3a5c7ea99b910121e;p=platform%2Fupstream%2Fgcc.git

doc: Document module language-linkage supported

I missed we documented this as unimplemented, when I implemented it.

	gcc/
	* doc/invoke.texi (C++ Modules): Remove language-linkage
	as missing feature.
---

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 50f5787..81d13f4 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -34639,13 +34639,6 @@ Papers p1815 (@uref{https://wg21.link/p1815}) and p2003
 exported region may reference (for instance, the entities an exported
 template definition may reference).  These are not fully implemented.
 
-@item Language-linkage module attachment
-Declarations with explicit language linkage (@code{extern "C"} or
-@code{extern "C++"}) are attached to the global module, even when in
-the purview of a named module.  This is not implemented.  Such
-declarations will be attached to the module, if any, in which they are
-declared.
-
 @item Standard Library Header Units
 The Standard Library is not provided as importable header units.  If
 you want to import such units, you must explicitly build them first.