public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Samuel Thibault <sthibaul@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] hurd: Initializy _dl_pagesize early in static builds
Date: Thu,  4 Jan 2024 22:49:53 +0000 (GMT)	[thread overview]
Message-ID: <20240104224953.79A9D3870849@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=fbfe0b20ab82550de65827e70aa89d8ae462b34d

commit fbfe0b20ab82550de65827e70aa89d8ae462b34d
Author: Sergey Bugaev <bugaevc@gmail.com>
Date:   Wed Jan 3 20:14:44 2024 +0300

    hurd: Initializy _dl_pagesize early in static builds
    
    We fetch __vm_page_size as the very first RPC that we do, inside
    __mach_init (). Propagate that to _dl_pagesize ASAP after that,
    before any other initialization.
    
    In dynamic builds, this is already done immediately after
    __mach_init (), inside _dl_sysdep_start ().
    
    Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
    Message-ID: <20240103171502.1358371-12-bugaevc@gmail.com>

Diff:
---
 sysdeps/mach/hurd/init-first.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/sysdeps/mach/hurd/init-first.c b/sysdeps/mach/hurd/init-first.c
index 26ccd37e55..22c357474a 100644
--- a/sysdeps/mach/hurd/init-first.c
+++ b/sysdeps/mach/hurd/init-first.c
@@ -162,6 +162,10 @@ first_init (void)
   /* Initialize data structures so we can do RPCs.  */
   __mach_init ();
 
+#ifndef SHARED
+  GLRO(dl_pagesize) = __vm_page_size;
+#endif
+
 #if USE_INIT1_TCBHEAD
   _hurd_tls_init (&__init1_tcbhead, 0);
 #endif

                 reply	other threads:[~2024-01-04 22:49 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=20240104224953.79A9D3870849@sourceware.org \
    --to=sthibaul@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: 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).