public inbox for
help / color / mirror / Atom feed
From: Nick Clifton <>
Subject: [binutils-gdb] Fix snafu in rust demangler recursion limit code
Date: Mon,  4 Jul 2022 15:28:21 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=96c33f79ded357e871c43af04238dfdedebac86c

commit 96c33f79ded357e871c43af04238dfdedebac86c
Author: Nick Clifton <>
Date:   Mon Jul 4 16:28:02 2022 +0100

    Fix snafu in rust demangler recursion limit code

 libiberty/rust-demangle.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libiberty/rust-demangle.c b/libiberty/rust-demangle.c
index d6daf23af27..8dfeeac2a4f 100644
--- a/libiberty/rust-demangle.c
+++ b/libiberty/rust-demangle.c
@@ -1234,6 +1234,7 @@ demangle_const (struct rust_demangler *rdm)
       PRINT (": ");
       PRINT (basic_type (ty_tag));
+  goto pass_return;
   rdm->errored = 1;

                 reply	other threads:[~2022-07-04 15:28 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).