public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Sunil Pandey <skpgkp2@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Use crtbeginT.o and crtend.o for non-PIE static executables
Date: Mon, 8 Apr 2024 09:23:28 -0700	[thread overview]
Message-ID: <CAMAf5_cGsqG_wEjyosOThEsbQFAqLfr8wzUGCcfoHW=j_HcSWQ@mail.gmail.com> (raw)
In-Reply-To: <20240405234257.2040273-1-hjl.tools@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

On Fri, Apr 5, 2024 at 4:43 PM H.J. Lu <hjl.tools@gmail.com> wrote:

> When static PIE is enabled by default, we shouldn't use crtbeginS.o and
> crtendS.o for non-PIE static executables.  Check $($(@F)-no-pie) to use
> crtbeginT.o and crtend.o to create non-PIE static executables.
> ---
>  Makeconfig | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/Makeconfig b/Makeconfig
> index 85e00cef94..e583765712 100644
> --- a/Makeconfig
> +++ b/Makeconfig
> @@ -705,13 +705,15 @@ endif
>  +prectorS = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtbeginS.o`
>  +postctorS = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtendS.o`
>  # Variants of the two previous definitions for statically linking
> programs.
> +static-prector = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtbeginT.o`
> +static-postctor = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtend.o`
>  ifeq (yes,$(enable-static-pie))
>  # Static PIE must use PIE variants.
> -+prectorT = $(+prectorS)
> -+postctorT = $(+postctorS)
> ++prectorT = $(if $($(@F)-no-pie),$(static-prector),$(+prectorS))
> ++postctorT = $(if $($(@F)-no-pie),$(static-postctor),$(+postctorS))
>  else
> -+prectorT = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtbeginT.o`
> -+postctorT = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtend.o`
> ++prectorT = $(static-prector)
> ++postctorT =$(static-postctor)
>  endif
>  csu-objpfx = $(common-objpfx)csu/
>  elf-objpfx = $(common-objpfx)elf/
> --
> 2.44.0
>

LGTM
Reviewed-by: Sunil K Pandey <skpgkp2@gmail.com>

--Sunil

      reply	other threads:[~2024-04-08 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 23:42 H.J. Lu
2024-04-08 16:23 ` Sunil Pandey [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='CAMAf5_cGsqG_wEjyosOThEsbQFAqLfr8wzUGCcfoHW=j_HcSWQ@mail.gmail.com' \
    --to=skpgkp2@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@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: 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).