public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64568] [5 Regression] error: invalid reference prefix
Date: Fri, 16 Jan 2015 09:01:00 -0000	[thread overview]
Message-ID: <bug-64568-4-8q5BXE7Vjh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64568-4@http.gcc.gnu.org/bugzilla/>

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...
>From gcc-bugs-return-473462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 16 09:08:10 2015
Return-Path: <gcc-bugs-return-473462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24665 invoked by alias); 16 Jan 2015 09:08:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24620 invoked by uid 48); 16 Jan 2015 09:08:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64622] convoluted loop codegen for __strcspn_c1
Date: Fri, 16 Jan 2015 09:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64622-4-ZPKtlxrV9P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64622-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64622-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg01456.txt.bz2
Content-length: 170

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd622

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
That's indeed more clever "loop header copying".


  parent reply	other threads:[~2015-01-16  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 13:40 [Bug middle-end/64568] New: " trippels at gcc dot gnu.org
2015-01-12 14:56 ` [Bug middle-end/64568] " rguenth at gcc dot gnu.org
2015-01-12 14:59 ` rguenth at gcc dot gnu.org
2015-01-12 15:26 ` trippels at gcc dot gnu.org
2015-01-13  8:32 ` rguenth at gcc dot gnu.org
2015-01-13  8:32 ` rguenth at gcc dot gnu.org
2015-01-16  9:01 ` trippels at gcc dot gnu.org [this message]
2015-01-16 10:52 ` trippels at gcc dot gnu.org
2015-01-16 13:26 ` rguenth at gcc dot gnu.org
2015-01-16 15:50 ` trippels at gcc dot gnu.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-64568-4-8q5BXE7Vjh@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).