From: Rich Felker <dalias@libc.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Initial xtensa/fdpic port review
Date: Wed, 28 Feb 2024 13:37:00 -0500 [thread overview]
Message-ID: <20240228183700.GP4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20240228183032.GO4163@brightrain.aerifal.cx>
On Wed, Feb 28, 2024 at 01:30:32PM -0500, Rich Felker wrote:
> On Wed, Feb 28, 2024 at 09:20:33AM -0800, Max Filippov wrote:
> >
> > > > p->relocated = 1;
> > > > }
> > > > @@ -1485,7 +1487,7 @@ void __libc_exit_fini()
> > > > if (dyn[0] & (1<<DT_FINI_ARRAY)) {
> > > > size_t n = dyn[DT_FINI_ARRAYSZ]/sizeof(size_t);
> > > > size_t *fn = (size_t *)laddr(p, dyn[DT_FINI_ARRAY])+n;
> > > > - while (n--) ((void (*)(void))*--fn)();
> > > > + while (n--) fpaddr(p, *--fn)();
> > >
> > > If this is fixable on the tooling side it really should be fixed
> > > there. init/fini arrays should have actual language-level function
> > > addresses (descriptor addresses on fdpic), not instruction addresses.
> >
> > I read libgcc code at
> > https://github.com/jcmvbkbc/gcc-xtensa/blob/xtensa-14-8789-fdpic/libgcc/crtstuff.c#L498-L503
> > and the way it's written suggests that this was done on purpose.
> > I put it into the WIP pile to figure out later what the purpose was.
> > I thought that SH might not have this issue because it just didn't
> > use the .array_init/.array_fini.
>
> I'm pretty sure we're using it -- musl-cross-make always forces it on
> via the gcc configure command line -- but it's possible there's some
> override disabling it for sh. I'll try some test cases and confirm
> whether sh is doing it right. Maybe the arm folks will have input on
> this too..?
Confirmed both that it works, and that it's working via init_array.
GCC emits:
.section .init_array,"aw"
.align 2
.long foo@FUNCDESC
for
__attribute__((__constructor__))
void foo() { ... }
Also, FWIW, I believe there's something of an application-facing
contract that you can declare function pointer arrays with
__attribute__((__section__(".init_array"))) and have them work, which
would not work if instruction addresses rather than function addresses
are expected to be there.
Rich
next prev parent reply other threads:[~2024-02-28 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 23:24 Rich Felker
2024-02-28 0:13 ` Rich Felker
2024-02-28 17:20 ` Max Filippov
2024-02-28 18:30 ` Rich Felker
2024-02-28 18:37 ` Rich Felker [this message]
2024-02-28 19:34 ` Max Filippov
2024-02-28 19:41 ` Max Filippov
2024-02-28 20:14 ` Rich Felker
2024-02-28 20:26 ` Rich Felker
2024-02-28 20:37 ` Rich Felker
2024-02-28 21:28 ` Max Filippov
2024-02-29 12:03 ` Max Filippov
2024-02-29 15:35 ` Rich Felker
2024-02-29 16:25 ` Max Filippov
2024-02-29 18:16 ` Rich Felker
2024-03-19 15:25 ` Max Filippov
2024-03-19 16:08 ` Max Filippov
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=20240228183700.GP4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=jcmvbkbc@gmail.com \
--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).