public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Xi Ruoyao <xry111@xry111.site>, libc-alpha@sourceware.org
Cc: Andrew Waterman <aswaterman@gmail.com>
Subject: Re: [PATCH v5 10/22] riscv: Fix Race conditions in pthread cancellation [BZ#12683]
Date: Tue, 11 Apr 2023 10:49:22 -0300	[thread overview]
Message-ID: <cf26915f-00c2-9319-4cbc-e1ea84fab9c9@linaro.org> (raw)
In-Reply-To: <6b71d9cc36d83450c8f39d3ce45bb75270f92d58.camel@xry111.site>



On 11/04/23 04:01, Xi Ruoyao wrote:
> On Tue, 2023-04-11 at 14:35 +0800, Xi Ruoyao wrote:
>> On Mon, 2023-04-10 at 17:46 -0300, Adhemerval Zanella via Libc-alpha
>> wrote:
>>> +1:
>>> +       addi    sp, sp, -16
>>> +       cfi_def_cfa_offset (16)
>>> +       REG_S   ra, (16-SZREG)(sp)
>>> +       cfi_offset (ra, -SZREG)
>>> +       call    __syscall_do_cancel
>>
>> Similarly to LoongArch, IMO this should simply be
>> "tail __syscall_do_cancel".
>>
>> Apparently _Noreturn is preventing GCC from generating a tail call for
>> RISC-V and LoongArch
> 
> Actually "everywhere" (but why the AArch64 code seems optimized?)

I hand optimized on some architectures, like x86_64 and aarch64.  For most
of the other architectures I just modeled after compiler generated call.

> 
>> so if you modeled the assembly following the GCC
>> output you'll get these sub-optimal things.  It seems a GCC bug to me.
> 
> It's https://gcc.gnu.org/PR10837 and closed as WONTFIX 20 years ago :(.
> And a comment from H.J. complained an impact on Glibc.
> 
> 

  reply	other threads:[~2023-04-11 13:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 19:58 [PATCH v5 00/22] " Adhemerval Zanella
2023-04-10 19:58 ` [PATCH v5 01/22] nptl: " Adhemerval Zanella
2023-04-10 19:58 ` [PATCH v5 02/22] x86_64: " Adhemerval Zanella
2023-04-10 19:58 ` [PATCH v5 03/22] x32: " Adhemerval Zanella
2023-04-10 19:58 ` [PATCH v5 04/22] i386: " Adhemerval Zanella
2023-04-10 19:58 ` [PATCH v5 05/22] aarch64: " Adhemerval Zanella
2023-04-10 19:58 ` [PATCH v5 06/22] arm: " Adhemerval Zanella
2023-04-10 19:58 ` [PATCH v5 07/22] powerpc: " Adhemerval Zanella
2023-04-14 15:27   ` Paul E Murphy
2023-04-27 11:13     ` Adhemerval Zanella Netto
2023-04-10 19:58 ` [PATCH v5 08/22] sparc: " Adhemerval Zanella
2023-04-10 20:46 ` [PATCH v5 09/22] s390: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 10/22] riscv: " Adhemerval Zanella
2023-04-11  6:35     ` Xi Ruoyao
2023-04-11  7:01       ` Xi Ruoyao
2023-04-11 13:49         ` Adhemerval Zanella Netto [this message]
2023-04-10 20:46   ` [PATCH v5 11/22] arc: Fix Race conditions in pthread cancellation [BZ #12683] Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 12/22] ia64: Fix Race conditions in pthread cancellation [BZ#12683] Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 13/22] sh: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 14/22] nios2: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 15/22] microblaze: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 16/22] hppa: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 17/22] m68k: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 18/22] alpha: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 19/22] csky: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 20/22] mips: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 21/22] or1k: " Adhemerval Zanella
2023-04-10 20:46   ` [PATCH v5 22/22] loongarch: " Adhemerval Zanella
2023-04-11  6:19     ` Xi Ruoyao
2023-04-11 12:00       ` caiyinyu
2023-04-11 12:21         ` caiyinyu
2023-04-11 12:55         ` Xi Ruoyao
2023-04-11 13:54           ` Adhemerval Zanella Netto
2023-04-11 13:56   ` [PATCH v5 09/22] s390: " Stefan Liebler

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=cf26915f-00c2-9319-4cbc-e1ea84fab9c9@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=aswaterman@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=xry111@xry111.site \
    /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).