public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/102426] [12 regression] Fix for PR 49664 breaks Solaris bootstrap with gld
Date: Tue, 22 Mar 2022 10:04:03 +0000 [thread overview]
Message-ID: <bug-102426-4-FoFCtPAY1D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102426-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102426
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:6ee5892638526366fc3d8a1f4426f3cc278ea061
commit r12-7752-g6ee5892638526366fc3d8a1f4426f3cc278ea061
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Mar 22 11:02:31 2022 +0100
lto-plugin: Use GNU ld or Solaris ld version script in preference to
-export-symbols-regex [PR102426]
As reported, libtool -export-symbols-regex doesn't work on Solaris
when using GNU ld instead of Sun ld, libtool just always assumes Sun ld.
As I'm unsure what is the maintainance status of libtool right now,
this patch solves it on the lto-plugin side instead, tests at configure
time
similar way how libssp and other target libraries test for symbol
versioning
(except omitting the symbol version because we just want one GLOBAL symbol
and rest of them LOCAL), and will use the current way of
-export-symbols-regex onload as fallback when this doesn't work.
2022-03-22 Jakub Jelinek <jakub@redhat.com>
PR lto/102426
lto-plugin/
* configure.ac (LTO_PLUGIN_USE_SYMVER, LTO_PLUGIN_USE_SYMVER_GNU,
LTO_PLUGIN_USE_SYMVER_SUN): New test for symbol versioning support.
* Makefile.am (version_arg, version_dep): Set conditionally based
on LTO_PLUGIN_USE_SYMVER*.
(liblto_plugin_la_LDFLAGS): Use $(version_arg) instead of
-export-symbols-regex onload.
(liblto_plugin_la_DEPENDENCIES): Depend on $(version_dep).
* lto-plugin.map: New file.
* configure: Regenerated.
* Makefile.in: Regenerated.
next prev parent reply other threads:[~2022-03-22 10:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 12:40 [Bug lto/102426] New: " ro at gcc dot gnu.org
2021-09-21 12:40 ` [Bug lto/102426] " ro at gcc dot gnu.org
2021-09-21 15:30 ` pinskia at gcc dot gnu.org
2021-09-21 17:38 ` pinskia at gcc dot gnu.org
2021-09-21 20:14 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-09-22 6:57 ` rguenth at gcc dot gnu.org
2021-10-27 9:05 ` pinskia at gcc dot gnu.org
2021-11-17 8:36 ` hubicka at gcc dot gnu.org
2021-11-17 8:44 ` pinskia at gcc dot gnu.org
2022-03-17 14:21 ` jakub at gcc dot gnu.org
2022-03-17 19:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-17 19:21 ` jakub at gcc dot gnu.org
2022-03-17 20:14 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-21 14:05 ` jakub at gcc dot gnu.org
2022-03-22 9:15 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-22 10:04 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-22 10:06 ` jakub at gcc dot gnu.org
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=bug-102426-4-FoFCtPAY1D@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).