From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79483 invoked by alias); 4 Dec 2018 17:08:04 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 77820 invoked by uid 89); 4 Dec 2018 17:08:03 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,KAM_SHORT,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*i:sk:c7c959c, H*f:sk:c7c959c X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 04 Dec 2018 17:08:02 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 5D0A130A7BB4; Tue, 4 Dec 2018 17:08:01 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id DE3EA5C21C; Tue, 4 Dec 2018 17:07:58 +0000 (UTC) Subject: Re: RFA/RFC: Add stack recursion limit to libiberty's demangler [v5] To: Nick Clifton , Ian Lance Taylor References: <87muprdko7.fsf@redhat.com> <20181130084211.GX12380@tucnak> <173817ca-0aa0-e1a2-6725-37e079ead545@redhat.com> <20181130140330.GA12380@tucnak> <460cb971-0e21-1e3e-4920-8b3ee7290cf7@redhat.com> <736e8303-b724-f96d-54f5-46bff99fa34d@redhat.com> <57d33aa7-4e37-a09c-4bdc-974b5f654d33@redhat.com> Cc: Richard Biener , Jakub Jelinek , matz@gcc.gnu.org, sgayou@redhat.com, Tom Tromey , GCC Patches , Binutils , Jason Merrill From: Pedro Alves Message-ID: Date: Tue, 04 Dec 2018 17:08:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-12/txt/msg00218.txt.bz2 On 12/04/2018 04:56 PM, Nick Clifton wrote: > Hi Pedro, > >> The issue pointed out by >> >> https://gcc.gnu.org/ml/gcc-patches/2018-11/msg02592.html >> >> is still present in this version. > > Doh! Yes I meant to fix that one too, but forgot. > >> Also, noticed a typo here: >> >>> +/* If DMGL_NO_RECURE_LIMIT is not enabled, then this is the value used as >> >> Typo: "RECURE" > > Oops - thanks. > > OK, revised (v5) patch attached. Is this version acceptable to all ? > This is fine with me. Thanks, Pedro Alves