From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85731 invoked by alias); 17 Dec 2015 14:01:37 -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 85720 invoked by uid 89); 17 Dec 2015 14:01:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=blow, hackers 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 (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 17 Dec 2015 14:01:30 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id ADD00349E45; Thu, 17 Dec 2015 14:01:29 +0000 (UTC) Received: from localhost.localdomain (ovpn-113-83.phx2.redhat.com [10.3.113.83]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tBHE1TCR030252; Thu, 17 Dec 2015 09:01:29 -0500 Subject: Re: libgcc: unwind-ia64.c without malloc/free To: Bernd Schmidt , Bernd Edlinger , "gcc-patches@gcc.gnu.org" References: <5670A86F.503@redhat.com> <5672B605.7020806@redhat.com> Cc: Steve Ellcey , Ian Lance Taylor From: Jeff Law Message-ID: <5672C038.7030800@redhat.com> Date: Thu, 17 Dec 2015 14:01:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5672B605.7020806@redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg01767.txt.bz2 On 12/17/2015 06:17 AM, Bernd Schmidt wrote: > On 12/17/2015 12:17 AM, Bernd Edlinger wrote: >> this is just an idea, how to avoid use of malloc in unwind-ia64.c. > [...] >> What do you think? > > Not worth worrying about IMO. I think ia64 is dead and best left to rest > in maintenance mode. Agreed. And in general using alloca is a problem waiting to happen unless you can prove there's no way to blow out the stack. I can't count the number of problems of that nature we've fixed in glibc over the last 5 years when the hackers realized that was a great attack vector. jeff