public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/10859: C++ style comments are not allowed in ISO C90 Date: Mon, 19 May 2003 12:56:00 -0000 [thread overview] Message-ID: <20030519125601.501.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/10859; it has been noted by GNATS. From: Andrew Pinski <pinskia@physics.uc.edu> To: ask@wisdom.weizmann.ac.il Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-gnats@gcc.gnu.org, "Gcc-Bugs@Gcc. Gnu. Org" <gcc-bugs@gcc.gnu.org> Subject: Re: bootstrap/10859: C++ style comments are not allowed in ISO C90 Date: Mon, 19 May 2003 08:52:57 -0400 This was my fault and it has been fixed. Please update you sources. This really should not be a warning at this point since the source of g++ depends on gcc extension so C++ style comments are also gcc extensions in g90. The sources of g++ should not have -pedantic on it. Thanks, Andrew Pinski PS Can someone close this bug as it has been fixed. On Monday, May 19, 2003, at 08:41 US/Eastern, ask@wisdom.weizmann.ac.il wrote: > >> Number: 10859 >> Category: bootstrap >> Synopsis: C++ style comments are not allowed in ISO C90 >> Confidential: no >> Severity: serious >> Priority: medium >> Responsible: unassigned >> State: open >> Class: sw-bug >> Submitter-Id: net >> Arrival-Date: Mon May 19 12:46:01 UTC 2003 >> Closed-Date: >> Last-Modified: >> Originator: Alexander Klimov >> Release: 3.4 20030519 >> Organization: >> Environment: > SunOS iridium 5.6 Generic_105181-32 sun4u sparc SUNW,Ultra-5_10 >> Description: > ../gcc/configure --prefix=/usr/local/gcc34 --with-cpu=ultrasparc > --enable-languages=c,c++ && make CFLAGS=-O2 'LIBCFLAGS=-g -O2' > 'LIBCXXFLAGS=-g -O2 -fno-implicit-templates' bootstrap > [...] > stage1/xgcc -Bstage1/ -B/usr/local/gcc34/sparc-sun-solaris2.6/bin/ -c > -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes > -Wmissing-prototypes -pedantic -Wno-long-long -Werror -Werror > -fno-common -DHAVE_CONFIG_H -I. -Icp -I../../gcc/gcc > -I../../gcc/gcc/cp -I../../gcc/gcc/config -I../../gcc/gcc/../include > ../../gcc/gcc/cp/name-lookup.c -o cp/name-lookup.o > ../../gcc/gcc/cp/name-lookup.c:108:32: C++ style comments are not > allowed in ISO C90 > ../../gcc/gcc/cp/name-lookup.c:108:32: (this will be reported only > once per input file) > make[2]: *** [cp/name-lookup.o] Error 1 > make[2]: Leaving directory `/export/home2/ask/build/gcc-build/gcc' > make[1]: *** [stage2_build] Error 2 > make[1]: Leaving directory `/export/home2/ask/build/gcc-build/gcc' > make: *** [bootstrap] Error 2 >> How-To-Repeat: > >> Fix: > >> Release-Note: >> Audit-Trail: >> Unformatted: > >
next reply other threads:[~2003-05-19 12:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-19 12:56 Andrew Pinski [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-19 13:03 ehrhardt 2003-05-19 12:46 ask
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=20030519125601.501.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).