From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14097 invoked by alias); 7 Jun 2011 14:00:00 -0000 Received: (qmail 14086 invoked by uid 22791); 7 Jun 2011 13:59:59 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 07 Jun 2011 13:59:42 +0000 Received: (qmail 16256 invoked from network); 7 Jun 2011 13:59:42 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 7 Jun 2011 13:59:42 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.72) (envelope-from ) id 1QTwom-0007yO-ID; Tue, 07 Jun 2011 13:59:40 +0000 Date: Tue, 07 Jun 2011 14:00:00 -0000 From: "Joseph S. Myers" To: Paolo Bonzini cc: Rainer Orth , gcc-patches@gcc.gnu.org, Ralf Wildenhues , Mike Stump , "Loren J. Rittle" , Kai Tietz , Dave Korn , Jason Thorpe , Krister Walfridsson , Uros Bizjak , Richard Henderson , Eric Botcazou Subject: Re: [build] Move ENABLE_EXECUTE_STACK to toplevel libgcc In-Reply-To: <4DE50FFB.90501@gnu.org> Message-ID: References: <4DE4AEC2.3030502@gnu.org> <4DE50FFB.90501@gnu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 X-SW-Source: 2011-06/txt/msg00519.txt.bz2 On Tue, 31 May 2011, Paolo Bonzini wrote: > > I'd thought about it, but refrained since HAVE_ENABLE_EXECUTE_STACK > > affects only three cpus. Currently, our documentation of libgcc > > configury and macros used is close to non-existant. That's probably for > > someone who has implemented this stuff. > > True, OTOH HAVE_ENABLE_EXECUTE_STACK is a target macro, and those are well > documented. Just say that it has to be defined if libgcc provides a > non-trivial implementation of __enable_execute_stack; it doesn't need to delve > into how to hack libgcc. As I understand it, HAVE_ENABLE_EXECUTE_STACK is only used in code under gcc/config/. That is, it is not a target macro as usually understood but is logically private to a few back ends (and it would be a bug to introduce uses of it elsewhere, just like it was a bug to introduce uses of TARGET_64BIT outside gcc/config/ when that macro also is logically private). -- Joseph S. Myers joseph@codesourcery.com