+2000-10-17 Marc Espie <espie@openbsd.org>
+
+ * invoke.texi (-shared): Insist on requiring code generation flags
+ to be used along with -shared, and document the subtle failure that
+ may occur otherwise.
+
2000-10-16 J. David Anglin <dave@hiauly1.hia.nrc.ca>
* pa.md (return_internal): Move `use' after `return'.
@item -shared
Produce a shared object which can then be linked with other objects to
-form an executable. Not all systems support this option. You must
-also specify @samp{-fpic} or @samp{-fPIC} on some systems when
-you specify this option.
+form an executable. Not all systems support this option. For predictable
+results, you must also specify the same set of options that were used to
+generate code (@samp{-fpic}, @samp{-fPIC}, or model suboptions)
+when you specify this option.@footnote{On some systems, @code{gcc -shared}
+needs to build supplementary stub code for constructors to work. On
+multi-libbed systems, @code{gcc -shared} must select the correct support
+libraries to link against. Failing to supply the correct flags may lead
+to subtle defects. Supplying them in cases where they are not necessary
+is innocuous.}
@item -symbolic
Bind references to global symbols when building a shared object. Warn