From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7690 invoked by alias); 7 May 2003 06:36:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 7671 invoked by uid 71); 7 May 2003 06:36:00 -0000 Resent-Date: 7 May 2003 06:36:00 -0000 Resent-Message-ID: <20030507063600.7670.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, bobf@mrp3.com Received: (qmail 5659 invoked by uid 48); 7 May 2003 06:29:50 -0000 Message-Id: <20030507062950.5658.qmail@sources.redhat.com> Date: Wed, 07 May 2003 06:36:00 -0000 From: bobf@mrp3.com Reply-To: bobf@mrp3.com To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: other/10659: docs need list of '#define' values generated by compiler X-SW-Source: 2003-05/txt/msg00444.txt.bz2 List-Id: >Number: 10659 >Category: other >Synopsis: docs need list of '#define' values generated by compiler >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: doc-bug >Submitter-Id: net >Arrival-Date: Wed May 07 06:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: bob frazier >Release: gcc 3.2.2 manual (on line) >Organization: >Environment: N/A (on-line documentation) >Description: I was unable to locate a page that described which pre-defined symbols were generated by the compiler. In some cases symbols (such as __STDC__ ) were mentioned in passing, but in no way could I find symbols to indicate what the CPU options were, optimization level of the compiler, or even simple ones like '__LINE__' (which you assume should be there) or '__cplusplus' (if the C++ compiler is being invoked, for 'dual use' headers). I am not even sure if I can rely on the use of '__cplusplus' either which is one of the things I was looking for. The other was the CPU type so that for SOME cpu's I'd have one kind of in-line assembler, and for other cpu's I'd have another kind, and for the rest I'd use C language (as an example). So, someplace in the documentation, please list all of the '#define' constants that the compiler generates, and the options that control them. Having them all on a single page would be nice... >How-To-Repeat: reference: http://gcc.gnu.org/onlinedocs/gcc-3.2.2/gcc/ >Fix: recommend adding page with '#define's generated by the compiler (based on compiler options or the actual language compilers being run). >Release-Note: >Audit-Trail: >Unformatted: