public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-8762] runtime: ignore __morestack function in runtime.Callers
Date: Tue, 13 Sep 2022 17:35:58 +0000 (GMT)	[thread overview]
Message-ID: <20220913173558.013DD3858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:21a3f43c6888b216ab70ef9aff5c3903ed1f218f

commit r12-8762-g21a3f43c6888b216ab70ef9aff5c3903ed1f218f
Author: Ian Lance Taylor <iant@golang.org>
Date:   Tue Sep 13 10:33:20 2022 -0700

    runtime: ignore __morestack function in runtime.Callers
    
    Backport from trunk.
    
    We were ignoring all functions starting with "__morestack_", but not
    the function "__morestack" itself.  Without this change, some tests
    such as recover.go started failing recently, though I'm not sure
    exactly what changed.
    
    Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/427935

Diff:
---
 libgo/runtime/go-callers.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libgo/runtime/go-callers.c b/libgo/runtime/go-callers.c
index 31783696a08..1d4dee66279 100644
--- a/libgo/runtime/go-callers.c
+++ b/libgo/runtime/go-callers.c
@@ -107,7 +107,7 @@ callback (void *data, uintptr_t pc, const char *filename, int lineno,
       p = function;
       if (__builtin_strncmp (p, "___", 3) == 0)
 	++p;
-      if (__builtin_strncmp (p, "__morestack_", 12) == 0)
+      if (__builtin_strncmp (p, "__morestack", 11) == 0)
 	return 0;
     }
   else if (filename != NULL)

                 reply	other threads:[~2022-09-13 17:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220913173558.013DD3858D28@sourceware.org \
    --to=ian@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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).