public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7679: The compiler crashes wen a right parentesis is missing Date: Sun, 29 Sep 2002 08:06:00 -0000 [thread overview] Message-ID: <20020929150600.29643.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7679; it has been noted by GNATS. From: =?iso-8859-1?Q?Pop_S=E9bastian?= <pop@gauvain.u-strasbg.fr> To: nathan@gcc.gnu.org, bmello@us.ibm.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/7679: The compiler crashes wen a right parentesis is missing Date: Sun, 29 Sep 2002 17:03:40 +0200 On Fri, Sep 13, 2002 at 10:11:57PM -0000, nathan@gcc.gnu.org wrote: > Synopsis: The compiler crashes wen a right parentesis is missing > > State-Changed-From-To: open->analyzed > State-Changed-By: nathan > State-Changed-When: Fri Sep 13 15:11:57 2002 > State-Changed-Why: > 3.2 & cvs go into an infinite loop > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7679 Tested with 3 gcc versions: seb@myp233:~/test/cp$ gcc-2.95 -v Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) seb@myp233:~/test/cp$ gcc-3.0 -v Reading specs from /usr/lib/gcc-lib/i386-linux/3.0.4/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc i386-linux Thread model: posix gcc version 3.0.4 seb@myp233:~/test/cp$ gcc-3.2 -v Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.1/specs Configured with: /mnt/data/gcc-3.1/gcc-3.2-3.2.1ds2/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-java-gc=boehm --enable-objc-gc i386-linux Thread model: posix gcc version 3.2.1 20020924 (Debian prerelease) Results for the original bug example: seb@myp233:~/test/cp$ gcc-2.95 -c pr7679.cc pr7679.cc: In method `double receptors::occupancy(int)': pr7679.cc:14: parse error before `;' Stops shortly. seb@myp233:~/test/cp$ gcc-3.0 -c pr7679.cc pr7679.cc: In member function `double receptors::occupancy(int)': pr7679.cc:14: parse error before `;' token Loops indefinitely. seb@myp233:~/test/cp$ gcc-3.2 -c pr7679.cc pr7679.cc: In member function `double receptors::occupancy(int)': pr7679.cc:14: parse error before `;' token Loops indefinitely. Also tested: struct f { int oo() { return (2; } }; Slightly simpler to analyse than the original bug example, and produces the same infinite loop. Note that gcc-3.2 stops correctly when it gets only the function declaration: int oo() { return (2; }
next reply other threads:[~2002-09-29 15:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-29 8:06 Pop Sébastian [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-23 14:57 mmitchel 2002-10-23 0:48 mmitchel 2002-09-13 15:11 nathan 2002-08-21 17:43 bmello
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=20020929150600.29643.qmail@sources.redhat.com \ --to=pop@gauvain.u-strasbg.fr \ --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).