public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dominique Devriese <dominique.devriese@student.kuleuven.ac.be>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: c++/10858: bogus compiler failure while compiling Boost.Python
Date: Mon, 19 May 2003 12:46:00 -0000	[thread overview]
Message-ID: <20030519124601.6093.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10858; it has been noted by GNATS.

From: Dominique Devriese <dominique.devriese@student.kuleuven.ac.be>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Cc:  
Subject: c++/10858: bogus compiler failure while compiling Boost.Python
Date: Mon, 19 May 2003 14:39:09 +0200

 >Number: 10858 >Category: c++ >Synopsis: bogus compiler failure while
 compiling Boost.Python >Confidential: no >Severity: serious >Priority:
 medium >Responsible: unassigned >State: open >Class: rejects-legal
 >Submitter-Id: net >Arrival-Date: Mon May 19 11:56:00 UTC 2003
 >Closed-Date: >Last-Modified: >Originator: Dominique Devriese
 >Release: 3.3 (Debian) (Debian testing/unstable) >Organization:
 >Environment: System: Linux appel 2.4.20-1-686 #1 Sat Mar 22 13:16:21
 EST 2003 i686 GNU/Linux Architecture: i686
 
 	
 host: i386-pc-linux-gnu build: i386-pc-linux-gnu target:
 i386-pc-linux-gnu configured with: ../src/configure -v
 --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang
 --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
 --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
 --with-system-zlib --enable-nls --without-included-gettext
 --enable-__cxa_atexit --enable-clocale=gnu --enable-debug
 --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc
 i386-linux >Description:
 	G++ 3.3 fails when compiling a certain c++ file from the
 	Boost.Python library.  The precise line is:
 
         BOOST_STATIC_ASSERT(
             sizeof(
                 convert_function_must_take_value_or_const_reference(&ToPython::convert,
                 1L))
             == sizeof(int));
 
 	which is precompiled to:
 
         typedef ::boost::static_assert_test<
         sizeof(::boost::STATIC_ASSERTION_FAILURE< (bool)( sizeof(
         convert_function_must_take_value_or_const_reference(&ToPython::convert,
         1L)) == sizeof(int) ) >)> boost_static_assert_typedef_31;
 
 	This gives the following output:
 
 domi: /tmp> g++ -c python_scripter.i
 /usr/include/boost/python/converter/as_to_python_function.hpp:28:
 sorry, unimplemented: `
    method_call_expr' not supported by dump_expr
    /usr/include/boost/python/converter/as_to_python_function.hpp:28:
    sorry, unimplemented: `
    method_call_expr' not supported by dump_expr
    /usr/include/boost/python/converter/as_to_python_function.hpp:28:
    sorry, unimplemented: `
    method_call_expr' not supported by dump_expr
    /usr/include/boost/python/converter/as_to_python_function.hpp:28:
    sorry, unimplemented: `
    method_call_expr' not supported by dump_expr
 
 	I'm not sure what this means, but GCC 3.2 does not reject the code:
 
 domi: /tmp> g++-3.2 -c python_scripter.3.2.i
 
 >How-To-Repeat:
 
 	Download the python_scripter.i file from
 	http://www.student.kuleuven.ac.be/~m0320063/python_scripter.i.bz2
 	bunzip2 it, and compile it as follows: 
 	"g++-3.3 -c python_scripter.i"
 
 >Fix:
 	No idea, sorry.  Hope you manage to fix it, and thanks in
 	advance.
 >Release-Note:
 >Audit-Trail:
 >Unformatted:


             reply	other threads:[~2003-05-19 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19 12:46 Dominique Devriese [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-19 11:56 Dominique Devriese

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=20030519124601.6093.qmail@sources.redhat.com \
    --to=dominique.devriese@student.kuleuven.ac.be \
    --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: 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).