public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: peter@peem.als.lbl.gov
To: gcc-gnats@gcc.gnu.org
Subject: c++/10192: <synopsis of the problem (one line)>
Date: Sun, 23 Mar 2003 04:36:00 -0000 [thread overview]
Message-ID: <200303230430.h2N4UVZs009485@peem.als.lbl.gov> (raw)
>Number: 10192
>Category: c++
>Synopsis: <synopsis of the problem (one line)>
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Mar 23 04:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Peter Schmid
>Release: 3.3 20030314 (prerelease)
>Organization:
LBL
>Environment:
System: Linux linux 2.4.19-4GB #1 Wed Nov 27 00:56:40 UTC 2002 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc3/gcc/configure --enable-threads=posix --enable-languages=c,c++,f77,objc --enable-__cxa_atexit
>Description:
According to my understanding of the documentation the compilation of
t.C should trigger a warning when the -Wformat option is active.
>How-To-Repeat:
source code t.C
/*
*/B2
*/
/*
*\/B2
*/
int main() {}
Compiling t.C
g++ -v --save-temps -Wcomment t.C
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3/specs
Configured with: ../gcc3/gcc/configure --enable-threads=posix --enable-languages=c,c++,f77,objc --enable-__cxa_atexit
Thread model: posix
gcc version 3.3 20030314 (prerelease)
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3/cc1plus -E -D__GNUG__=3 -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=0 -D_GNU_SOURCE t.C -Wcomment t.ii
ignoring nonexistent directory "NONE/include"
ignoring nonexistent directory "/usr/local/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include/c++/3.3
/usr/local/include/c++/3.3/i686-pc-linux-gnu
/usr/local/include/c++/3.3/backward
/usr/local/include
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3/include
/usr/include
End of search list.
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3/cc1plus -fpreprocessed t.ii -quiet -dumpbase t.C -auxbase t -Wcomment -version -o t.s
GNU C++ version 3.3 20030314 (prerelease) (i686-pc-linux-gnu)
compiled by GNU C version 3.3 20030314 (prerelease).
GGC heuristics: --param ggc-min-expand=47 --param ggc-min-heapsize=31901
t.C:3: error: syntax error before `*' token
preprocessed header file t.ii
# 1 "t.C"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "t.C"
B2
*/
int main() {}
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2003-03-23 4:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200303230430.h2N4UVZs009485@peem.als.lbl.gov \
--to=peter@peem.als.lbl.gov \
--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: link
Be 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).