From: "Marc Poulhiès" <poulhies@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: "Kévin Le Gouguec" <legouguec@adacore.com>
Subject: [COMMITED] ada: Document support for the mold linker
Date: Mon, 26 Sep 2022 11:15:16 +0200 [thread overview]
Message-ID: <20220926091516.273390-1-poulhies@adacore.com> (raw)
From: Kévin Le Gouguec <legouguec@adacore.com>
gcc/ada/
* doc/gnat_ugn/building_executable_programs_with_gnat.rst
(Linker Switches): Document support for mold along with gold; add some
advice regarding OpenSSL in the Pro version.
* gnat_ugn.texi: Regenerate.
---
...building_executable_programs_with_gnat.rst | 28 +++++++++++++++++--
gcc/ada/gnat_ugn.texi | 10 +++----
2 files changed, 30 insertions(+), 8 deletions(-)
diff --git a/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst b/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
index 6a478095cfc..f675732aae2 100644
--- a/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
+++ b/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
@@ -6229,11 +6229,33 @@ Linker switches can be specified after :switch:`-largs` builder switch.
.. index:: -fuse-ld=name
:switch:`-fuse-ld={name}`
- Linker to be used. The default is ``bfd`` for :file:`ld.bfd`,
- the alternative being ``gold`` for :file:`ld.gold`. The later is
- a more recent and faster linker, but only available on GNU/Linux
+ Linker to be used. The default is ``bfd`` for :file:`ld.bfd`; ``gold``
+ (for :file:`ld.gold`) and ``mold`` (for :file:`ld.mold`) are more
+ recent and faster alternatives, but only available on GNU/Linux
platforms.
+ .. only:: PRO
+
+ The GNAT distribution for native Linux platforms includes ``mold``,
+ compiled against OpenSSL version 1.1; however, the distribution does
+ not include OpenSSL. In order to use this linker, you may either:
+
+ * use your system's OpenSSL library, if the version matches: in this
+ situation, you need not do anything beside using the
+ :switch:`-fuse-ld=mold` switch,
+
+ * obtain a source distribution for OpenSSL 1.1, compile the
+ :file:`libcrypto.so` library and install it in the directory of
+ your choice, then include this directory in the
+ :envvar:`LD_LIBRARY_PATH` environment variable,
+
+ * install another copy of ``mold`` by other means in the directory
+ of your choice, and include this directory in the :envvar:`PATH`
+ environment variable; you may find this alternative preferable if
+ the copy of ``mold`` included in GNAT does not suit your needs
+ (e.g. being able to link against your system's OpenSSL, or using
+ another version of ``mold``).
+
.. _Binding_with_gnatbind:
Binding with ``gnatbind``
diff --git a/gcc/ada/gnat_ugn.texi b/gcc/ada/gnat_ugn.texi
index f2cb1ed638a..d7bcf74e278 100644
--- a/gcc/ada/gnat_ugn.texi
+++ b/gcc/ada/gnat_ugn.texi
@@ -19,7 +19,7 @@
@copying
@quotation
-GNAT User's Guide for Native Platforms , Sep 09, 2022
+GNAT User's Guide for Native Platforms , Sep 26, 2022
AdaCore
@@ -15317,10 +15317,11 @@ Linker switches can be specified after @code{-largs} builder switch.
@item @code{-fuse-ld=`name'}
-Linker to be used. The default is @code{bfd} for @code{ld.bfd},
-the alternative being @code{gold} for @code{ld.gold}. The later is
-a more recent and faster linker, but only available on GNU/Linux
+Linker to be used. The default is @code{bfd} for @code{ld.bfd}; @code{gold}
+(for @code{ld.gold}) and @code{mold} (for @code{ld.mold}) are more
+recent and faster alternatives, but only available on GNU/Linux
platforms.
+
@end table
@node Binding with gnatbind,Linking with gnatlink,Linker Switches,Building Executable Programs with GNAT
@@ -17932,7 +17933,6 @@ instr.ads
-
@c -- Example: A |withing| unit has a |with| clause, it |withs| a |withed| unit
@node GNAT and Program Execution,Platform-Specific Information,GNAT Utility Programs,Top
--
2.25.1
reply other threads:[~2022-09-26 9:15 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=20220926091516.273390-1-poulhies@adacore.com \
--to=poulhies@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=legouguec@adacore.com \
/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).