From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28072 invoked by alias); 18 Aug 2017 18:22:57 -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 28058 invoked by uid 89); 18 Aug 2017 18:22:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=BAYES_00,RCVD_IN_BRBL_LASTEXT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy= X-HELO: smtp.eu.adacore.com Received: from mel.act-europe.fr (HELO smtp.eu.adacore.com) (194.98.77.210) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 18 Aug 2017 18:22:54 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id 89E5882462; Fri, 18 Aug 2017 20:22:52 +0200 (CEST) Received: from smtp.eu.adacore.com ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExiHOEORtrtr; Fri, 18 Aug 2017 20:22:52 +0200 (CEST) Received: from arcturus.home (a2413-adsl2.pck.nerim.net [213.41.134.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.eu.adacore.com (Postfix) with ESMTPSA id 409108244C; Fri, 18 Aug 2017 20:22:52 +0200 (CEST) From: Eric Botcazou To: Jeff Law Cc: gcc-patches@gcc.gnu.org, Richard Biener Subject: Re: Ping on target independent stack clash protection patches Date: Fri, 18 Aug 2017 19:21:00 -0000 Message-ID: <2931569.9yq3OuhAv1@arcturus.home> User-Agent: KMail/4.14.10 (Linux/3.16.7-53-desktop; KDE/4.14.9; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2017-08/txt/msg01147.txt.bz2 > #01 of #08: > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01971.html > > #02 of #08: > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01972.html > > #03 of #08: > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01974.html > > Need to reach some kind of closure on these, then I can start pinging > the target maintainers for the rest of the bits... All OK with me, thanks for your attention to the interaction with Ada. Minor nit: + Stack checking is designed to detect infinite recursion for Ada + programs. Furthermore stack checking tries to ensure that scenario + that enough stack space is left to run a signal handler. Let's use the same wording as in invoke.texi: "...infinite recursion and stack overflows for...". Missing "in" before "that scenario'. [Ada folks in the embedded world are mainly scared about the possibility of tasks (threads) overwriting each other's stack; in that case, their only requirement is to be able to run a last chance handler to terminate the task properly. But the ACATS testsuite contains a handul of tests that litteraly play with stack overflows and this complicates the implementation for artificial reasons]. -- Eric Botcazou