public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/azanella/clang] nptl: x86_64: Use __builtin_frame_address for CURRENT_STACK_FRAME
Date: Tue, 29 Mar 2022 20:24:40 +0000 (GMT)	[thread overview]
Message-ID: <20220329202440.0288C388458B@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5d56904f8b9c92c105c5cbe2a41c6d287d9f4f14

commit 5d56904f8b9c92c105c5cbe2a41c6d287d9f4f14
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Tue Mar 8 17:31:08 2022 -0300

    nptl: x86_64: Use __builtin_frame_address for CURRENT_STACK_FRAME

Diff:
---
 sysdeps/x86/nptl/pthreaddef.h | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/sysdeps/x86/nptl/pthreaddef.h b/sysdeps/x86/nptl/pthreaddef.h
index 63fdbcb27c..9de2ea9326 100644
--- a/sysdeps/x86/nptl/pthreaddef.h
+++ b/sysdeps/x86/nptl/pthreaddef.h
@@ -39,10 +39,4 @@
 
 
 /* Location of current stack frame.  */
-#ifdef __x86_64__
-/* The frame pointer is not usable.  */
-# define CURRENT_STACK_FRAME \
-  ({ register char *frame __asm__("rsp"); frame; })
-#else
-# define CURRENT_STACK_FRAME	__builtin_frame_address (0)
-#endif
+#define CURRENT_STACK_FRAME __builtin_frame_address (0)


             reply	other threads:[~2022-03-29 20:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 20:24 Adhemerval Zanella [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-09 21:15 Adhemerval Zanella
2022-06-09 13:11 Adhemerval Zanella
2022-06-03 14:01 Adhemerval Zanella
2022-05-13 14:14 Adhemerval Zanella
2022-05-12 19:28 Adhemerval Zanella
2022-05-10 18:19 Adhemerval Zanella
2022-04-29 13:59 Adhemerval Zanella
2022-04-04 12:49 Adhemerval Zanella
2022-03-31 19:01 Adhemerval Zanella
2022-03-16 17:59 Adhemerval Zanella
2022-03-15 18:37 Adhemerval Zanella
2022-03-11 17:21 Adhemerval Zanella
2022-03-10 19:20 Adhemerval Zanella

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=20220329202440.0288C388458B@sourceware.org \
    --to=azanella@sourceware.org \
    --cc=glibc-cvs@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).