public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Alistair Francis <alistair.francis@wdc.com>
Cc: GNU C Library <libc-alpha@sourceware.org>, Zong Li <zongbox@gmail.com>
Subject: Re: [PATCH 06/18] RISC-V: Add path of library directories for the 32-bit
Date: Thu, 2 Apr 2020 14:48:51 -0700	[thread overview]
Message-ID: <CAFyWVaYAqPoYHK9m1EFKeb75BB+N9JGEGYNjvbHvrL=DcOViyQ@mail.gmail.com> (raw)
In-Reply-To: <20200402162939.358617-7-alistair.francis@wdc.com>

On Thu, Apr 2, 2020 at 9:38 AM Alistair Francis via Libc-alpha
<libc-alpha@sourceware.org> wrote:
> diff --git a/sysdeps/unix/sysv/linux/riscv/dl-cache.h b/sysdeps/unix/sysv/linux/riscv/dl-cache.h
> index c297dfe84f..60fc172edb 100644
> --- a/sysdeps/unix/sysv/linux/riscv/dl-cache.h
> +++ b/sysdeps/unix/sysv/linux/riscv/dl-cache.h
> @@ -34,6 +34,8 @@
>     RISC-V, libraries can be found in paths ending in:
>       - /lib64/lp64d
>       - /lib64/lp64
> +     - /lib32/ilp32d
> +     - /lib32/ilp32
>       - /lib (only ld.so)
>     so this will add all of those paths.
>

FYI This reminds me of something.  I was forwarded a complaint that
the RISC-V ABI was violating the Filesystem Hierarchy Standard (FHS),
which specifies that libraries are only allowed to be in /lib and
/lib<qual>.  The complaint was that /lib64/lp64d doesn't follow this
pattern, and hence is a violation of this standard.  However, the
standard doesn't clearly state that <qual> can't contain a slash.  The
person who complained insisted that it was implied.  It wasn't clear
to me what to do with the complaint.  Changing the ABI now would be
rather disruptive and undesirable, and I also don't know how important
the FHS standard is, or whether this interpretation is correct.

http://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html

Jim

  reply	other threads:[~2020-04-02 21:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 16:29 [PATCH 00/18] glibc port for 32-bit RISC-V (RV32) Alistair Francis
2020-04-02 16:29 ` [PATCH 01/18] RISC-V: Use 64-bit time_t and off_t for RV32 and RV64 Alistair Francis
2020-04-02 16:29 ` [PATCH 02/18] RISC-V: Define __NR_* as __NR_*_time64/64 for 32-bit Alistair Francis
2020-04-02 16:29 ` [PATCH 03/18] RISC-V: Add support for 32-bit vDSO calls Alistair Francis
2020-04-02 16:29 ` [PATCH 04/18] RISC-V: Add socket-constants.h for RV32 Alistair Francis
2020-04-02 16:29 ` [PATCH 05/18] RISC-V: Support dynamic loader for the 32-bit Alistair Francis
2020-04-02 16:29 ` [PATCH 06/18] RISC-V: Add path of library directories " Alistair Francis
2020-04-02 21:48   ` Jim Wilson [this message]
2020-04-02 22:57     ` Alistair Francis
2020-04-02 23:33       ` Jim Wilson
2020-04-03  9:51         ` Zong Li
2020-04-03 16:01     ` Maciej W. Rozycki
2020-04-03 18:04       ` Jim Wilson
2020-04-02 16:29 ` [PATCH 07/18] RISC-V: Add arch-syscall.h for RV32 Alistair Francis
2020-04-02 16:29 ` [PATCH 08/18] RISC-V: nptl: update default pthread-offsets.h Alistair Francis
2020-04-02 16:29 ` [PATCH 09/18] RISC-V: The ABI implementation for 32-bit Alistair Francis

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='CAFyWVaYAqPoYHK9m1EFKeb75BB+N9JGEGYNjvbHvrL=DcOViyQ@mail.gmail.com' \
    --to=jimw@sifive.com \
    --cc=alistair.francis@wdc.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zongbox@gmail.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.
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).