public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bobf@mrp3.com To: gcc-gnats@gcc.gnu.org Subject: other/10659: docs need list of '#define' values generated by compiler Date: Wed, 07 May 2003 06:36:00 -0000 [thread overview] Message-ID: <20030507062950.5658.qmail@sources.redhat.com> (raw) >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:
next reply other threads:[~2003-05-07 6:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-07 6:36 bobf [this message] 2003-05-07 7:22 neil 2003-05-07 7:26 Andris Pavenis
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030507062950.5658.qmail@sources.redhat.com \ --to=bobf@mrp3.com \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).