public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwgk at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13549] New: Regression compiling Boost.Python test
Date: Fri, 02 Jan 2004 18:48:00 -0000 [thread overview]
Message-ID: <20040102184817.13549.rwgk@yahoo.com> (raw)
gcc snapshot from 2003/12/30, ca. 7:40am PST
Configured with: ../gcc/configure --prefix=/usr/local_cci/gcc_cvs_2003_12_30 --
enable-languages=c,c++
Redhat Linux 8.0
One of our regression test for Boost.Python does not compile with g++
(GCC) 3.4.0 20031230 (experimental). We are puzzled by the error
message. David Abrahams, principle author of the Boost.Python library,
writes:
>I don't have a clue. It seems to be failing to find the overload of
>the get function in make_constructor.hpp.
>
><shrug>
The same code works with many other compilers incl. earlier gcc's. I
will attach a preprocessed file that can be used to reproduce the
problem:
% g++ -fPIC -ftemplate-depth-120 -w -DNDEBUG -O3 -DBOOST_PYTHON_MAX_BASES=2 -
I/net/worm/scratch1/rwgk/rc1310/boost -I/usr/include/python2.2 -
E /net/worm/scratch1/rwgk/rc1310/boost/libs/python/test/injected.cpp >
injected_pp.cpp
% g++ -fPIC -ftemplate-depth-120 -w -O3 injected_pp.cpp >& injected_pp_error
% g++ -fPIC -ftemplate-depth-120 -w -O3 injected_pp.cpp |& perl
~/stlfilt/gSTLFilt.pl > injected_pp_error_stlfilt
The files are also available here:
http://cci.lbl.gov/~rwgk/bugs/gcc340/injected_pp.cpp
http://cci.lbl.gov/~rwgk/bugs/gcc340/injected_pp_error
http://cci.lbl.gov/~rwgk/bugs/gcc340/injected_pp_error_stlfilt
The full source code (complete boost tree, release candidate branch for
version 1.31.0) is also available:
http://cci.lbl.gov/~rwgk/bugs/gcc340/boost_rc1310_2004_01_02_1016.tar.gz
Remark: the release candidate is patched already to work around
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13530
--
Summary: Regression compiling Boost.Python test
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rwgk at yahoo dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: g++ (GCC) 3.4.0 20031230 (experimental)
GCC host triplet: i686-gnu-linux
GCC target triplet: i686-gnu-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13549
next reply other threads:[~2004-01-02 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 18:48 rwgk at yahoo dot com [this message]
2004-01-02 18:49 ` [Bug c++/13549] " rwgk at yahoo dot com
2004-01-02 18:50 ` rwgk at yahoo dot com
2004-01-02 18:51 ` rwgk at yahoo dot com
2004-01-02 19:05 ` rwgk at yahoo dot com
2004-01-02 21:16 ` pinskia at gcc dot gnu dot org
2004-01-02 22:25 ` [Bug c++/13549] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-01-02 22:40 ` dave at boost-consulting dot com
2004-01-03 1:49 ` pinskia at gcc dot gnu dot org
2004-01-03 2:55 ` dave at boost-consulting dot com
2004-01-03 3:00 ` pinskia at gcc dot gnu dot org
2004-01-04 23:02 ` [Bug c++/13549] Problem " mmitchel at gcc dot gnu dot org
2004-02-16 5:22 ` pinskia at gcc dot gnu dot org
2004-02-23 1:06 ` pinskia at gcc dot gnu dot org
2004-03-06 14:19 ` Woebbeking at web dot de
2004-03-06 19:15 ` giovannibajo at libero dot it
2004-05-26 17:13 ` 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=20040102184817.13549.rwgk@yahoo.com \
--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: 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).