public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Vincent Chen <vincent.chen@sifive.com>
To: libc-alpha@sourceware.org, palmer@dabbelt.com,
	darius@bluespec.com, andrew@sifive.com, dj@redhat.com
Cc: kito.cheng@sifive.com, greentime.hu@sifive.com,
	Vincent Chen <vincent.chen@sifive.com>
Subject: [PATCH v2 0/2] RISC-V: Add vector ISA support
Date: Tue, 18 Jan 2022 12:31:57 +0800	[thread overview]
Message-ID: <20220118043159.27521-1-vincent.chen@sifive.com> (raw)

According to the feedback for the version 1 patch set, only the
"RISC-V: Remove riscv-specific sigcontext.h" patch remains in this version
patch set. It means that MINSIGSTKSZ, SIGSTKSZ, and PTHREAD_STACK_MIN are not
changed after introducing the V-extension support. Therefore, the current
definition of the above stack size is insufficient to backup all vector
registers. In this circumstance, users have to use the mechanisms submitted by
H.J. Lu https://sourceware.org/git/?p=glibc.git;a=commit;h=6c57d320484988e87e446e2e60ce42816bf51d53
and https://sourceware.org/git/?p=glibc.git;a=commit;h=5d98a7dae955bafa6740c26eaba9c86060ae0344
to obtain the appropriate size of the current system setting.

Besides, a new calling convention using vector registers to transfer argument
or return value probably be proposed in the feature. It may cause the resolved
functions and audit functions to corrupt the content of the vector registers,
which are used as argument registers and address return registers. To avoid
this problem, this patch set includes Hsiangkai Wang's patch to enable the
Glibc dynamic loader to directly resolve the function symbols whose calling
convention is incompatible with the standard calling convention. The
corresponding implementation in Binutils can be found in
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=8155b8539b55bca87378129e02009cd8907d8c8c.


Hsiangkai Wang (1):
  riscv: Resolve symbols directly for symbols with STO_RISCV_VARIANT_CC.

Vincent Chen (1):
  RISC-V: remove riscv-specific sigcontext.h

 elf/elf.h                                     |  7 +++++
 manual/platform.texi                          |  6 +++++
 .../sigcontext.h => riscv/dl-dtprocnum.h}     | 22 +++++-----------
 sysdeps/riscv/dl-machine.h                    | 26 +++++++++++++++++++
 4 files changed, 45 insertions(+), 16 deletions(-)
 rename sysdeps/{unix/sysv/linux/riscv/bits/sigcontext.h => riscv/dl-dtprocnum.h} (55%)

-- 
2.17.1


             reply	other threads:[~2022-01-18  4:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  4:31 Vincent Chen [this message]
2022-01-18  4:31 ` [PATCH v2 1/2] RISC-V: remove riscv-specific sigcontext.h Vincent Chen
2022-01-20  2:36   ` Palmer Dabbelt
2022-01-20  2:47     ` Kito Cheng
2022-01-21  1:29       ` Vincent Chen
2022-01-24  9:42         ` Vincent Chen
2022-02-24 20:56         ` Palmer Dabbelt
2022-02-25  0:32           ` Vincent Chen
2022-01-18  4:31 ` [PATCH v2 2/2] riscv: Resolve symbols directly for symbols with STO_RISCV_VARIANT_CC Vincent Chen
2022-01-20  2:21   ` Palmer Dabbelt
2022-01-20  2:38     ` H.J. Lu
2022-01-20  2:43       ` Palmer Dabbelt
2022-01-21  1:43     ` Vincent Chen
2022-02-24 20:56       ` Palmer Dabbelt
2022-12-09  4:11   ` Vineet Gupta
2022-12-09  4:22     ` Kito Cheng
2022-12-09  4:26       ` Vineet Gupta
2022-12-09  4:35         ` Kito Cheng

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=20220118043159.27521-1-vincent.chen@sifive.com \
    --to=vincent.chen@sifive.com \
    --cc=andrew@sifive.com \
    --cc=darius@bluespec.com \
    --cc=dj@redhat.com \
    --cc=greentime.hu@sifive.com \
    --cc=kito.cheng@sifive.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palmer@dabbelt.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).