From: "Alex Rønne Petersen" <alex@alexrp.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] i386, x86_64: Set the symbol type for the START function.
Date: Sat, 22 Feb 2025 01:40:25 +0100 [thread overview]
Message-ID: <CAH9TF6PrMGvhAWS-HDdWyZA-QnyjwiwBem-XMV1-eN2LvNUndg@mail.gmail.com> (raw)
In-Reply-To: <20250222003026.GG1827@brightrain.aerifal.cx>
On Sat, Feb 22, 2025 at 1:30 AM Rich Felker <dalias@libc.org> wrote:
>
> On Sat, Nov 23, 2024 at 01:19:51AM +0100, Alex Rønne Petersen wrote:
> > As for other architectures. Noticed this while running Zig's gen_stubs.zig tool.
> > ---
> > arch/i386/crt_arch.h | 1 +
> > arch/x86_64/crt_arch.h | 1 +
> > 2 files changed, 2 insertions(+)
> >
> > diff --git a/arch/i386/crt_arch.h b/arch/i386/crt_arch.h
> > index 43c8477a..1a80fce3 100644
> > --- a/arch/i386/crt_arch.h
> > +++ b/arch/i386/crt_arch.h
> > @@ -3,6 +3,7 @@ __asm__(
> > ".weak _DYNAMIC \n"
> > ".hidden _DYNAMIC \n"
> > ".global " START "\n"
> > +".type " START ",%function \n"
> > START ":\n"
> > " xor %ebp,%ebp \n"
> > " mov %esp,%eax \n"
> > diff --git a/arch/x86_64/crt_arch.h b/arch/x86_64/crt_arch.h
> > index 3eec61bd..b1c9c476 100644
> > --- a/arch/x86_64/crt_arch.h
> > +++ b/arch/x86_64/crt_arch.h
> > @@ -1,6 +1,7 @@
> > __asm__(
> > ".text \n"
> > ".global " START " \n"
> > +".type " START ",%function \n"
> > START ": \n"
> > " xor %rbp,%rbp \n"
> > " mov %rsp,%rdi \n"
> > --
> > 2.40.1
>
> Looks ok but was missing x32. I'll add it when merging.
Oops, I sent a v2 of the patch that includes x32, but didn't send it
as a reply to this one, sorry.
prev parent reply other threads:[~2025-02-22 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 0:19 Alex Rønne Petersen
2025-02-22 0:30 ` Rich Felker
2025-02-22 0:40 ` Alex Rønne Petersen [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=CAH9TF6PrMGvhAWS-HDdWyZA-QnyjwiwBem-XMV1-eN2LvNUndg@mail.gmail.com \
--to=alex@alexrp.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).