From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id 6B9E93858407 for ; Tue, 22 Mar 2022 17:01:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6B9E93858407 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=suse.cz Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 449701F388; Tue, 22 Mar 2022 17:01:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1647968506; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Cfrj5uq/Xo9Rt7A4FamJi5qtU3uQfBrT+CQMBB8tejs=; b=2B3jOT/kPHuMHxf2larPQVIaaFkMKIqUZmFrxr+uiNYzdOkjB7gguAppIs8LoEa2S9FdXp 6Uq9dwChLYpReYp/mQWhDUeCY/d0hoFm6KXl/rF+WkRYxKdhesFha65kNZoB/mvo7arpjl ftcV08XsT6xuIpx5EnTLGTv9LrefYCo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1647968506; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Cfrj5uq/Xo9Rt7A4FamJi5qtU3uQfBrT+CQMBB8tejs=; b=V2UIArqPCGV6uzThhShpiTOLPv3vtiSuMA73ZFVF52GnlaG6f15A9EE4umog84e97438aR VMkmtcyjCpQCWOAQ== Received: from suse.cz (virgil.suse.cz [10.100.13.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 2C4E5A3B87; Tue, 22 Mar 2022 17:01:46 +0000 (UTC) From: Martin Jambor To: Krishna Narayanan Cc: gcc@gcc.gnu.org Subject: Re: GSoC: cp demangle non recursive In-Reply-To: References: User-Agent: Notmuch/0.35 (https://notmuchmail.org) Emacs/27.2 (x86_64-suse-linux-gnu) Date: Tue, 22 Mar 2022 18:01:46 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2022 17:01:48 -0000 Hello, On Sat, Mar 19 2022, Krishna Narayanan wrote: > Hello, > I have a doubt regarding the recursion part in demangle.c, what should > be the expected report when the recursion limit has been > reached, Look at the comment of the d_demangle function. In the new scheme of things, the failure would essentially be a memory allocation failure. > Secondly the verbose which has to be printed for the C > linkage, what should be the info that has to be displayed. I'm not sure I understand, but the demangler should have exactly the same output as now, only the internal implementation should change. Good luck, Martin