public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53451] New: [4.8 regression] ICE verify_gimple failed
Date: Tue, 22 May 2012 12:38:00 -0000	[thread overview]
Message-ID: <bug-53451-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53451

             Bug #: 53451
           Summary: [4.8 regression] ICE verify_gimple failed
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vincenzo.innocente@cern.ch


requires boost
(p.s. last working version of 4.8 for what I'm concerned is revision 187326)

cat ice2205.cc 
#include <vector>
#include <algorithm>
#include <boost/bind/bind.hpp>


struct A {
  int i;
};

bool foo(std::vector<A> const & va, int q) {
   auto it = std::find_if(va.begin(), va.end(), boost::bind(&A::i, _1) == q);
  return it != va.end();
} 
[vocms123] ~/public/ctest/bugs48 $ c++ -v
Using built-in specs.
COLLECT_GCC=c++
COLLECT_LTO_WRAPPER=/afs/cern.ch/user/i/innocent/w3/gcc47slc5/libexec/gcc/x86_64-unknown-linux-gnu/4.8.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-trunk/configure --enable-languages=c,c++,fortran
--disable-multilib --enable-gold=yes --disable-nls --enable-lto
--with-mpc=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--with-gmp=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--with-mpfr=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--prefix=/afs/cern.ch/user/i/innocent/w3/gcc47slc5
--with-build-time-tools=/build/ge/new-binutils/a/slc5_amd64_gcc470/external/gcc/4.7.0-cms/bin
Thread model: posix
gcc version 4.8.0 20120522 (experimental) [trunk revision 187760] (GCC) 

[vocms123] ~/public/ctest/bugs48 $ c++ -std=c++11 -c ice2205.cc
-I/build/ge/new-binutils/a/slc5_amd64_gcc470/external/boost/1.49.0-cms3/include
In file included from
/build/ge/new-binutils/a/slc5_amd64_gcc470/external/boost/1.49.0-cms3/include/boost/mem_fn.hpp:22:0,
                 from
/build/ge/new-binutils/a/slc5_amd64_gcc470/external/boost/1.49.0-cms3/include/boost/bind/bind.hpp:26,
                 from ice2205.cc:3:
/build/ge/new-binutils/a/slc5_amd64_gcc470/external/boost/1.49.0-cms3/include/boost/bind/mem_fn.hpp:
In member function 'const R& boost::_mfi::dm<R, T>::operator()(const T&) const
[with R = int; T = A]':
/build/ge/new-binutils/a/slc5_amd64_gcc470/external/boost/1.49.0-cms3/include/boost/bind/mem_fn.hpp:362:15:
error: invalid types in nop conversion
     R const & operator()(T const & t) const
               ^
sizetype
<<< Unknown tree: offset_type >>>
D.66000 = (sizetype) D.65999;

/build/ge/new-binutils/a/slc5_amd64_gcc470/external/boost/1.49.0-cms3/include/boost/bind/mem_fn.hpp:362:15:
internal compiler error: verify_gimple failed


             reply	other threads:[~2012-05-22 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 12:38 vincenzo.innocente at cern dot ch [this message]
2012-05-22 12:50 ` [Bug c++/53451] " rguenth at gcc dot gnu.org
2012-05-22 13:21 ` vincenzo.innocente at cern dot ch

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-53451-4@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: 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).