This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: visibility control for explicit instantiations
On Jul 21, 2006, at 1:01 PM, Jason Merrill wrote:
Sure. I'd move the added text to its own paragraph at the end of
the description and drop the "Note however that".
Ok, thanks. Curious, that was the version just before I moved it
up... :-) I checked the man page formatting to ensure it was sane
as well. This is what went in:
2006-07-21 Mike Stump <mrs@apple.com>
* doc/invoke.texi (C++ Dialect Options): Note that
-fvisibility-inlines-hidden doesn't affect explicitly
instantiationed inline methods.
Doing diffs in doc:
--- doc/invoke.texi.~1~ 2006-07-20 15:43:45.000000000 -0700
+++ doc/invoke.texi 2006-07-21 13:15:18.000000000 -0700
@@ -1627,6 +1627,10 @@ effect of the switch for that method. F
compare pointers to a particular inline method, you might mark it as
having default visibility.
+Explicitly instantiated inline methods are unaffected by this option
+as their linkage might otherwise cross a shared library boundary.
+@xref{Template Instantiation}.
+
@item -fno-weak
@opindex fno-weak
Do not use weak symbol support, even if it is provided by the linker.
--------------