public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rdiezmail-gcc at yahoo dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98324] [11 Regression] bootstrap broken with a LTO build configured with --enable-default-pie Date: Wed, 15 Dec 2021 14:34:41 +0000 [thread overview] Message-ID: <bug-98324-4-altQBNEzOl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98324-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98324 R. Diez <rdiezmail-gcc at yahoo dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rdiezmail-gcc at yahoo dot de --- Comment #7 from R. Diez <rdiezmail-gcc at yahoo dot de> --- I have been building cross-compiler toolchains for years with makefiles similar to this one: https://github.com/rdiez/JtagDue/blob/master/Toolchain/Makefile I am trying to upgrade that makefile from GCC 10.2 to GCC 11.2, and I am getting exactly the same problem that this bug describes. I checked, and the fix linked from this bug is included in version 11.2 . However, I have never used option "--enable-default-pie" in the past, and I was able build cross-toolchains with many GCC versions without it for years. The target is actually an embedded ARM Cortex-M3 microcontroller with fixed memory addresses (a "bare metal" firmware without OS), so I guess that I do not really need PIE. It may even cost some performance, if I understand what PIE does. I am guessing that bootstrapping a cross-compiler GCC is still broken with its default PIE setting.
prev parent reply other threads:[~2021-12-15 14:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-16 17:34 [Bug bootstrap/98324] New: " doko at debian dot org 2020-12-16 17:56 ` [Bug bootstrap/98324] " nathan at gcc dot gnu.org 2020-12-16 20:14 ` nathan at gcc dot gnu.org 2020-12-21 14:33 ` nathan at gcc dot gnu.org 2020-12-22 13:22 ` nathan at gcc dot gnu.org 2020-12-23 8:23 ` doko at debian dot org 2020-12-23 12:55 ` cvs-commit at gcc dot gnu.org 2020-12-23 12:56 ` nathan at gcc dot gnu.org 2021-12-15 14:34 ` rdiezmail-gcc at yahoo dot de [this message]
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-98324-4-altQBNEzOl@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).