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 c++/29408] New: [4.1 regression] parse error for valid code Date: Tue, 10 Oct 2006 01:17:00 -0000 [thread overview] Message-ID: <bug-29408-5724@http.gcc.gnu.org/bugzilla/> (raw) works with 4.0.4, 4.1.1, 4.2.0, fails with 4.1 branch 20061008 $ g++ -c -Wall -fPIC -fexceptions -frtti -I/usr/include/python2.3 -I/usr/share/python2.3/CXX -I/usr/include/subversion-1 -I/usr/include/apr-1.0 -I. -DNDEBUG -o pysvn.o pysvn.cpp /usr/include/python2.3/CXX/Objects.hxx:1932: error: parse error in template argument list -- Summary: [4.1 regression] parse error for valid code Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ 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=29408
next reply other threads:[~2006-10-10 1:17 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-10 1:17 debian-gcc at lists dot debian dot org [this message] 2006-10-10 1:18 ` [Bug c++/29408] " debian-gcc at lists dot debian dot org 2006-10-10 5:01 ` pinskia at gcc dot gnu dot org 2006-10-10 8:53 ` rguenth at gcc dot gnu dot org 2006-10-10 16:30 ` pinskia at gcc dot gnu dot org 2006-10-10 18:04 ` debian-gcc at lists dot debian dot org 2006-10-10 18:26 ` debian-gcc at lists dot debian dot org 2006-10-12 0:37 ` [Bug c++/29408] [4.1/4.2 " debian-gcc at lists dot debian dot org 2006-10-12 3:58 ` pinskia at gcc dot gnu dot org 2006-10-12 4:27 ` bangerth at dealii dot org 2006-10-15 21:21 ` mmitchel at gcc dot gnu dot org 2006-10-16 17:28 ` mmitchel at gcc dot gnu dot org 2006-10-16 23:08 ` mmitchel at gcc dot gnu dot org 2006-10-16 23:12 ` [Bug c++/29408] [4.1 " mmitchel at gcc dot gnu dot org 2006-10-17 0:01 ` mmitchel at gcc dot gnu dot org 2006-10-17 0:01 ` mmitchel 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-29408-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).