https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64568

Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #6 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
I still happens running the Boost testsuite on ppc64:


trippels@gcc2-power8 status % g++ -c -O3 -std=c++11 test22.ii
In file included from ../libs/numeric/ublas/test/test2.hpp:22:0,
                 from ../libs/numeric/ublas/test/test22.cpp:13:
../boost/numeric/ublas/blas.hpp: In function ‘M&
boost::numeric::ublas::blas_2::hr2(M&, const T&, const V1&, const V2&) [with M
= boost::numeric::ublas::matrix<std::complex<double> >; T =
std::complex<double>; V1 = boost::numeric::ublas::vector<std::complex<double>
>; V2 = boost::numeric::ublas::vector<std::complex<double> >]’:
../boost/numeric/ublas/blas.hpp:330:13: error: invalid reference prefix
         M & hr2 (M &m, const T &t, const V1 &v1, const V2 &v2)
             ^
MEM[base: _216, index: ivtmp.1531_157, offset: 0]
cc1plus: note: in statement
# VUSE <.MEM_156>
_158 = IMAGPART_EXPR <MEM[base: _216, index: ivtmp.1531_157, offset: 0]>;
../boost/numeric/ublas/blas.hpp:330:13: error: invalid reference prefix
MEM[base: _216, index: ivtmp.1531_157, offset: 0]
cc1plus: note: in statement
# VUSE <.MEM_156>
_91 = REALPART_EXPR <MEM[base: _216, index: ivtmp.1531_157, offset: 0]>;
../boost/numeric/ublas/blas.hpp:330:13: internal compiler error: verify_gimple
failed
0x10a48a6f verify_gimple_in_cfg(function*, bool)
        ../../gcc/gcc/tree-cfg.c:5069
0x10903e53 execute_function_todo
        ../../gcc/gcc/passes.c:1955
0x10904a93 do_per_function
        ../../gcc/gcc/passes.c:1647
0x10904d67 execute_todo
        ../../gcc/gcc/passes.c:2012
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.


Reducing...

Reply via email to