public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ronghua at iu dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105115] `demangle_const` causes infinite recursion and stack overflow Date: Tue, 17 May 2022 18:22:53 +0000 [thread overview] Message-ID: <bug-105115-4-NlesvsgU1o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105115-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105115 --- Comment #1 from ronghua at iu dot edu --- Hello, It's already more than one month since my post, and the bug still exists at latest commit (e.i. e84412c6a3c3eed1a4eca5fe18f329bfa7efea40), so I would like to know why it is still `UNCONFIRMED`. Thanks.
next prev parent reply other threads:[~2022-05-17 18:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-31 0:32 [Bug c++/105115] New: " ronghua at iu dot edu 2022-05-17 18:22 ` ronghua at iu dot edu [this message] 2022-05-17 20:44 ` [Bug c++/105115] " ronghua at iu dot edu
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=bug-105115-4-NlesvsgU1o@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).