public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] nptl: x86_64: Use same code for CURRENT_STACK_FRAME and stackinfo_get_sp
Date: Tue, 30 Aug 2022 16:08:31 -0300	[thread overview]
Message-ID: <253763f9-99ff-947c-e01e-eae8095c7163@linaro.org> (raw)
In-Reply-To: <CAFUsyfLocF58AtOaZHWuQZ8BP8iOUWUR4N5M7ggj2nHpV1zbCg@mail.gmail.com>



On 30/08/22 15:54, Noah Goldstein wrote:
> On Tue, Aug 30, 2022 at 5:08 AM Adhemerval Zanella via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>>
>> It avoids the possible warning of uninitialized 'frame' variable when
>> building with clang:
>>
>>   ../sysdeps/nptl/jmp-unwind.c:27:42: error: variable 'frame' is
>>   uninitialized when used here [-Werror,-Wuninitialized]
>>     __pthread_cleanup_upto (env->__jmpbuf, CURRENT_STACK_FRAME);
>>
>> The resulting code is similar to CURRENT_STACK_FRAME.
>>
>> Checked on x86_64-linux-gnu.
>> ---
>>  sysdeps/x86/nptl/pthreaddef.h | 4 +++-
>>  sysdeps/x86_64/stackinfo.h    | 4 +++-
>>  2 files changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/sysdeps/x86/nptl/pthreaddef.h b/sysdeps/x86/nptl/pthreaddef.h
>> index 63fdbcb27c..7df65931a3 100644
>> --- a/sysdeps/x86/nptl/pthreaddef.h
>> +++ b/sysdeps/x86/nptl/pthreaddef.h
>> @@ -42,7 +42,9 @@
>>  #ifdef __x86_64__
>>  /* The frame pointer is not usable.  */
>>  # define CURRENT_STACK_FRAME \
>> -  ({ register char *frame __asm__("rsp"); frame; })
>> +  ({ register void * p__ __asm__(RSP_REG); \
>> +     asm volatile("" : "=r" (p__)); \
>> +     p__; })
>>  #else
>>  # define CURRENT_STACK_FRAME   __builtin_frame_address (0)
>>  #endif
>> diff --git a/sysdeps/x86_64/stackinfo.h b/sysdeps/x86_64/stackinfo.h
>> index 34c9d0b576..7354632132 100644
>> --- a/sysdeps/x86_64/stackinfo.h
>> +++ b/sysdeps/x86_64/stackinfo.h
>> @@ -40,7 +40,9 @@
>>     for which they need to act as barriers as well, hence the additional
>>     (unnecessary) parameters.  */
>>  #define stackinfo_get_sp() \
>> -  ({ void *p__; asm volatile ("mov %%" RSP_REG ", %0" : "=r" (p__)); p__; })
>> +  ({ register void * p__ __asm__(RSP_REG); \
>> +     asm volatile("" : "=r" (p__)); \
>> +     p__; })
> 
> This change addresses a different issue. Maybe two separate commits?

I am not sure this characterizes as an 'issue', since code does work as is,
the idea is to have the same definition.

> 
> Otherwise LGTM.
>>  #define stackinfo_sub_sp(ptr) \
>>    ({ ptrdiff_t d__;                                            \
>>       asm volatile ("sub %%" RSP_REG " , %0" : "=r" (d__) : "0" (ptr)); \
>> --
>> 2.34.1
>>

  reply	other threads:[~2022-08-30 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 12:07 Adhemerval Zanella
2022-08-30 18:54 ` Noah Goldstein
2022-08-30 19:08   ` Adhemerval Zanella Netto [this message]
2022-08-30 19:43     ` Noah Goldstein

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=253763f9-99ff-947c-e01e-eae8095c7163@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=goldstein.w.n@gmail.com \
    --cc=libc-alpha@sourceware.org \
    /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).