From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29655 invoked by alias); 24 Apr 2002 12:51:24 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 29630 invoked from network); 24 Apr 2002 12:51:21 -0000 Received: from unknown (HELO mail.redhat.de) (193.103.254.4) by sources.redhat.com with SMTP; 24 Apr 2002 12:51:21 -0000 Message-ID: <3CC6AA46.3060304@redhat.com> Date: Wed, 24 Apr 2002 06:36:00 -0000 From: Manfred Hollstein X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Scholz Maik (CM-CR/EES3) *" Cc: "'gcc@gcc.gnu.org'" Subject: Re: howto use -fstack-check References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg01237.txt.bz2 Scholz Maik (CM-CR/EES3) * wrote: > what is "gccint.info"? It's the documentation of gcc internals. This is from a current gcc-3.1 snapshot: This manual documents the internals of the GNU compilers, including how to port them to new targets and some information about how to write front ends for new languages. It corresponds to GCC version 3.1. The use of the GNU compilers is documented in a separate manual. *Note Introduction: (gcc)Top. This manual is mainly a reference manual rather than a tutorial. It discusses how to contribute to GCC (*note Contributing::), the characteristics of the machines supported by GCC as hosts and targets (*note Portability::), how GCC relates to the ABIs on such systems (*note Interface::), and the characteristics of the languages for which GCC front ends are written (*note Languages::). It then describes the GCC source tree structure and build system, some of the interfaces to GCC front ends, and how support for a target system is implemented in GCC. Additional tutorial information is linked to from `http://gcc.gnu.org/readings.html'. > > Regards > > Maik Cheers. l8er manfred