From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-477255-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 56776 invoked by alias); 4 May 2018 16:42:13 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 56751 invoked by uid 89); 4 May 2018 16:42:12 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FROM_EXCESS_BASE64,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=
X-HELO: mail-qt0-f182.google.com
Received: from mail-qt0-f182.google.com (HELO mail-qt0-f182.google.com) (209.85.216.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 04 May 2018 16:42:11 +0000
Received: by mail-qt0-f182.google.com with SMTP id f5-v6so14798790qth.2        for <gcc-patches@gcc.gnu.org>; Fri, 04 May 2018 09:42:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:content-transfer-encoding;        bh=C48RMtMbwYFBmEF8aZK4oiTWdjBtVHZ+LP3zcwSL5ug=;        b=tWQgI3LIuxwefI7unSA0v5R3+D3q9s3pmj0KY6nbm7E0KW1p/iX724cqJkdsHKNLeQ         YD9vQplYghJEGLNop8XrARdZD0e7M9Vpt0Sk0wisU8JKJwKfPBXmy5C6V2SPLj9VAdpb         Hcy+1q0UafhPwdPXg+/sZa/T4qg5ywCMlmu42LwvmEyKm9Y4v0gnAETM19agJvOppL0t         sAoTeuwDSYWIhmZ6Rz3pr7OOUvyPmHnKBoAZaHFWhxqChtwnb+085ANcztRYa9PAkDEz         gS31/7R36fa4y9RKL4vOVrVzYjSY2zd1WAKXdZRHU0PbZ3ld8z0IYSm9pN2EZqCreSId         dvEA==
X-Gm-Message-State: ALQs6tDqMpMdyo/siAVEdRdtizdw/JWRCrnOcHGoppTjh5U1UhxEITmc	XsWFFAIkbIOfhxnUkZO4GfuSfJSEOf3MHKRIBIYL67SL
X-Google-Smtp-Source: AB8JxZrfESZVMBN/u6oUb3znskXfOjSG08gSA9XIhW2JGH5Rkea6H03JHyAibVuXpTCenSaL0QM7w4HTsOXFimA1RdQ=
X-Received: by 2002:ac8:10d:: with SMTP id e13-v6mr23427037qtg.403.1525452129149; Fri, 04 May 2018 09:42:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.36.225 with HTTP; Fri, 4 May 2018 09:41:48 -0700 (PDT)
In-Reply-To: <fe36645b-165e-4829-a60b-6581266dedf0@parmance.com>
References: <fe36645b-165e-4829-a60b-6581266dedf0@parmance.com>
From: =?UTF-8?B?UGVra2EgSsOkw6Rza2Vsw6RpbmVu?= <pekka@parmance.com>
Date: Fri, 04 May 2018 16:42:00 -0000
Message-ID: <CAJk11WDkhEJTsmyXPGbmagXvAFuvuBpLPHaOko-sdKrvzFdcMQ@mail.gmail.com>
Subject: Re: [PATCH 1/8] [BRIGFE] fix an alloca stack underflow
To: GCC Patches <gcc-patches@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2018-05/txt/msg00228.txt.bz2

Committed as r259942.

On Fri, May 4, 2018 at 4:56 PM, Pekka J=C3=A4=C3=A4skel=C3=A4inen <pekka@pa=
rmance.com> wrote:
> We didn't preserve additional space for the alloca frame pointers that
> are needed to be saved in the alloca space.