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: Make init-first.c no longer x86-specific Date: Thu, 4 Jan 2024 22:49:43 +0000 (GMT) [thread overview] Message-ID: <20240104224943.342A83870897@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9eaa0e179962a10db91fe566753fc38623097dbe commit 9eaa0e179962a10db91fe566753fc38623097dbe Author: Sergey Bugaev <bugaevc@gmail.com> Date: Wed Jan 3 20:14:42 2024 +0300 hurd: Make init-first.c no longer x86-specific This will make it usable in other ports. Signed-off-by: Sergey Bugaev <bugaevc@gmail.com> Message-ID: <20240103171502.1358371-10-bugaevc@gmail.com> Diff: --- sysdeps/mach/hurd/{x86 => }/init-first.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sysdeps/mach/hurd/x86/init-first.c b/sysdeps/mach/hurd/init-first.c similarity index 98% rename from sysdeps/mach/hurd/x86/init-first.c rename to sysdeps/mach/hurd/init-first.c index 211b2096b6..8526191692 100644 --- a/sysdeps/mach/hurd/x86/init-first.c +++ b/sysdeps/mach/hurd/init-first.c @@ -1,4 +1,4 @@ -/* Initialization code run first thing by the ELF startup code. For x86/Hurd. +/* Initialization code run first thing by the ELF startup code. For Hurd. Copyright (C) 1995-2024 Free Software Foundation, Inc. This file is part of the GNU C Library. @@ -155,7 +155,7 @@ first_init (void) #ifndef SHARED /* In the static case, we need to set up TLS early so that the stack - protection guard can be read at gs:0x14 by the gcc-generated snippets. */ + protection guard can be read at from TLS by the GCC-generated snippets. */ _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=20240104224943.342A83870897@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: 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).