mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [RFC v3 1/1] xtensa: add port
Date: Mon, 6 May 2024 18:15:24 -0400	[thread overview]
Message-ID: <20240506221524.GJ10433@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAMo8BfJdH3rcTDZAF58AScjXnEXLDQo0PotsYVU4tNWAy75Eow@mail.gmail.com>

On Mon, May 06, 2024 at 02:47:45PM -0700, Max Filippov wrote:
> On Mon, May 6, 2024 at 1:57 PM Rich Felker <dalias@libc.org> wrote:
> >
> > On Mon, May 06, 2024 at 11:01:12AM -0700, Max Filippov wrote:
> > > Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> > > ---
> > > Changes v2->v3:
> > > - fix semid_ds::sem_nsems type
> > > - drop store to GOT entry at offset 12 from arch/xtensa/crt_arch.h
> > > - add alignment to all assembly function entry points
> > > - add .literal_position directive to vfork
> >
> > Can you elaborate on what .literal_position does here?
> 
> It's an xtensa-specific assembler directive that indicates where
> the assembler may place literals when --text-section-literals
> and --auto-litpools options are used. vfork implementation has
> two movi instructions that are relaxed into literal loads and thus
> may need this hint. I've discovered that it's missing when building
> the toolchain with other target options produced build error in
> vfork.s

OK.

> > > diff --git a/arch/xtensa/reloc.h b/arch/xtensa/reloc.h
> > > new file mode 100644
> > > index 000000000000..cd7a455a2d9c
> > > --- /dev/null
> > > +++ b/arch/xtensa/reloc.h
> > > @@ -0,0 +1,32 @@
> > > +#if __FDPIC__
> > > +#define ABI_SUFFIX "-fdpic"
> > > +#else
> > > +#define ABI_SUFFIX ""
> > > +#endif
> > > +
> > > +#define LDSO_ARCH "xtensa" ABI_SUFFIX
> >
> > The ldso name is still missing endianness, if it's intended that both
> > be supported. It needs to completely identify the ABI whenever there
> > are incompatible ABI variants.
> 
> For each xtensa core there's only one fixed endianness and code
> built for one xtensa core is not supposed to be used for any other
> core, so it's not an issue, right?

Yes, it is an issue. The ldsonames for ABIs must be globally unique.
They are intended to be installable in a filesystem shared between
multiple archs, possibly even unrelated archs executed via qemu-user
or similar.

Rich

  reply	other threads:[~2024-05-06 22:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 18:01 [musl] [RFC v3 0/1] xtensa FDPIC port Max Filippov
2024-05-06 18:01 ` [musl] [RFC v3 1/1] xtensa: add port Max Filippov
2024-05-06 20:58   ` Rich Felker
2024-05-06 21:47     ` Max Filippov
2024-05-06 22:15       ` Rich Felker [this message]
2024-05-06 22:40         ` Max Filippov
2024-05-06 22:55           ` Rich Felker
2024-05-06 23:28             ` Max Filippov
2024-05-06 23:59               ` Rich Felker
2024-05-07  0:40                 ` Max Filippov
2024-05-07  1:37                   ` Rich Felker
2024-05-07 15:30                     ` Max Filippov
2024-05-07 16:27                       ` Rich Felker
2024-05-07 18:41                         ` Max Filippov
2024-05-08 17:39                           ` 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=20240506221524.GJ10433@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).