public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/24916] New: option -O undocumented in cpp docs Date: Thu, 17 Nov 2005 17:52:00 -0000 [thread overview] Message-ID: <bug-24916-5724@http.gcc.gnu.org/bugzilla/> (raw) [forwarded from http://bugs.debian.org/339495] you can see[1] that cpp supports -O, -O[1-9], -Os options, and these options are meaningful (defining macros). but this is not documented in man page[2] and info[3]. [1] $ cpp -dM /dev/null | grep OPT $ cpp -dM -O /dev/null | grep OPT #define __OPTIMIZE__ 1 $ cpp -dM -Os /dev/null | grep OPT #define __OPTIMIZE__ 1 #define __OPTIMIZE_SIZE__ 1 $ cpp -dM -O2 /dev/null | grep OPT #define __OPTIMIZE__ 1 [2] /usr/share/man/man1/cpp-4.0.1.gz [3] /usr/share/info/cpp-4.0.info.gz -- Summary: option -O undocumented in cpp docs Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: preprocessor AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: debian-gcc at lists dot debian dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24916
next reply other threads:[~2005-11-17 17:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-17 17:52 debian-gcc at lists dot debian dot org [this message] 2005-11-17 18:02 ` [Bug c/24916] " pinskia at gcc dot gnu dot org 2005-11-17 18:03 ` pinskia at gcc dot gnu dot org 2005-11-17 18:04 ` pinskia at gcc dot gnu dot org 2005-11-17 18:05 ` pinskia at gcc dot gnu dot org 2005-11-17 18:26 ` debian-gcc at lists dot debian dot org 2005-11-17 18:33 ` pinskia at gcc dot gnu dot org 2005-11-17 18:34 ` pinskia at gcc dot gnu dot org
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=bug-24916-5724@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).