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 target/96190] --enable-default-pie on sparc uses crtbeginS.o (correct) and crtend.o (incorrect) Date: Thu, 23 Jul 2020 23:07:03 +0000 [thread overview] Message-ID: <bug-96190-4-VyJq83vieo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96190-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96190 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Sergei Trofimovich <slyfox@gcc.gnu.org>: https://gcc.gnu.org/g:ca47325f300462b6f4ea84de2103eef81a4a7684 commit r10-8527-gca47325f300462b6f4ea84de2103eef81a4a7684 Author: Sergei Trofimovich <siarheit@google.com> Date: Thu Jul 23 23:58:35 2020 +0100 sparc/sparc64: use crtendS.o for default-pie executables [PR96190] In --enable-default-pie mode compiler should switch from using crtend.o to crtendS.o. On sparc it is especially important because crtend.o contains PIC-unfriendly code. We use GNU_USER_TARGET_ENDFILE_SPEC as a baseline spec to get crtendS.o instead of crtend.o in !no-pie mode. gcc: 2020-07-14 Sergei Trofimovich <siarheit@google.com> PR target/96190 * config/sparc/linux.h (ENDFILE_SPEC): Use GNU_USER_TARGET_ENDFILE_SPEC to get crtendS.o for !no-pie mode. * config/sparc/linux64.h (ENDFILE_SPEC): Ditto. (cherry picked from commit 87891d5eafe8d1de90b9d9b056eca81c508d1c77)
next prev parent reply other threads:[~2020-07-23 23:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-13 23:12 [Bug driver/96190] New: " slyfox at inbox dot ru 2020-07-14 7:02 ` [Bug target/96190] " slyfox at inbox dot ru 2020-07-20 19:47 ` cvs-commit at gcc dot gnu.org 2020-07-20 21:48 ` slyfox at inbox dot ru 2020-07-23 23:07 ` cvs-commit at gcc dot gnu.org [this message] 2020-07-25 20:12 ` slyfox 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-96190-4-VyJq83vieo@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).