public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <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 09:15:24 +0000	[thread overview]
Message-ID: <bug-102426-4-iVEmpvpUJa@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 #12 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Created attachment 52656
>   --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52656&action=edit
> gcc12-pr102426.patch
>
> So like this then?

I included the patch in last night's bootstraps (sparc-sun-solaris2.11,
as/ld, gas/ld, and i386-pc-solaris2.11, as/ld, gas/ld, gas/gld).  Worked
fine: in all cases, the only exported global symbol is onload, as
expected.

Thanks.

In the end, there isn't much point in building the lto-plugin when
Solaris ld (or any linker not supporting the gld/gold plugin interface)
is in use.  I think I checked at one point if this could be fitted in
with the linker's support and/or auditing interfaces

https://docs.oracle.com/cd/E37838_01/html/E36783/chapter6-1238.html#scrolltoc

but cannot find my notes anymore and, I believe, concluded that they
don't match.

  parent reply	other threads:[~2022-03-22  9:15 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 [this message]
2022-03-22 10:04 ` cvs-commit at gcc dot gnu.org
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-iVEmpvpUJa@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).