public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/99097] profiledbootstrap fails with LTO and disabled plugin Date: Mon, 15 Feb 2021 09:56:05 +0000 [thread overview] Message-ID: <bug-99097-4-Hsj3QkFRLp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99097-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99097 --- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to Jan Hubicka from comment #3) > > I've just tried to reproduce it: > > ../configure --with-build-config=bootstrap-lto --enable-checking=release > > --disable-plugin > > > > But the build is fine for me. Ah, my bad, I used BFD. > On our dhcp230 (zen III machine) it works if you make system linker ld, > if system linker is gold (from tumbleweed) it fails > > GNU gold (GNU Binutils 2.36.50.20210211) 1.16 Note that this isn't ld.gold from openSUSE Tumbleweed. We still have 2.35.1 release in the distribution. This must be a built gold from source files?
next prev parent reply other threads:[~2021-02-15 9:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-14 17:54 [Bug middle-end/99097] New: " hubicka at gcc dot gnu.org 2021-02-14 18:03 ` [Bug middle-end/99097] " hubicka at gcc dot gnu.org 2021-02-15 9:20 ` marxin at gcc dot gnu.org 2021-02-15 9:41 ` Jan Hubicka 2021-02-15 9:41 ` hubicka at ucw dot cz 2021-02-15 9:51 ` rguenth at gcc dot gnu.org 2021-02-15 9:56 ` marxin at gcc dot gnu.org [this message] 2021-02-15 10:12 ` Jan Hubicka 2021-02-15 10:12 ` hubicka at ucw dot cz 2021-02-15 10:25 ` marxin at gcc dot gnu.org 2021-02-18 11:07 ` marxin 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-99097-4-Hsj3QkFRLp@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: linkBe 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).