public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Makeconfig: Set pie-ccflag to -fPIE by default [BZ# 29514] Date: Mon, 29 Aug 2022 13:05:51 +0000 (GMT) [thread overview] Message-ID: <20220829130551.5C3DD3858D37@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=51231c469b49fb3837590f40a93f88db9a20bb86 commit 51231c469b49fb3837590f40a93f88db9a20bb86 Author: Richard Henderson <richard.henderson@linaro.org> Date: Tue Aug 23 13:49:23 2022 -0700 Makeconfig: Set pie-ccflag to -fPIE by default [BZ# 29514] We should default to the larger code model, in order to support larger applications built with -static -pie. This should be consistent with pic-ccflag, which defaults to -fPIC. Remove the now redundant override from sysdeps/sparc/Makefile. Note that -fno-pie and -fno-PIE have the same effect. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Tested-by: Carlos O'Donell <carlos@redhat.com> Diff: --- Makeconfig | 2 +- sysdeps/sparc/Makefile | 3 --- 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/Makeconfig b/Makeconfig index e78cf220af..f8164a0025 100644 --- a/Makeconfig +++ b/Makeconfig @@ -1052,7 +1052,7 @@ pic-ccflag = -fPIC PIC-ccflag = -fPIC endif # This can be changed by a sysdep makefile -pie-ccflag = -fpie +pie-ccflag = -fPIE no-pie-ccflag = -fno-pie # This one should always stay like this unless there is a very good reason. PIE-ccflag = -fPIE diff --git a/sysdeps/sparc/Makefile b/sysdeps/sparc/Makefile index 12c2c1b085..26b4a84606 100644 --- a/sysdeps/sparc/Makefile +++ b/sysdeps/sparc/Makefile @@ -1,9 +1,6 @@ # The Sparc `long double' is a distinct type we support. long-double-fcts = yes -pie-ccflag = -fPIE -no-pie-ccflag = -fno-PIE - ifeq ($(subdir),gmon) sysdep_routines += sparc-mcount endif
reply other threads:[~2022-08-29 13:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220829130551.5C3DD3858D37@sourceware.org \ --to=carlos@sourceware.org \ --cc=glibc-cvs@sourceware.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).