[Bug c++/65851] New: ice in set_lattice_value at tree-ssa-cc p.c:535

["dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>]

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

            Bug ID: 65851
           Summary: ice in set_lattice_value at tree-ssa-cc p.c:535
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com

Created attachment 35386
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35386&action=edit
gzipped C++ source code

The attached code, when compiled by gcc trunk dated 20150422, 
with flag -O2 on x86_64, does this

bug201.cc: In member function ‘void CamWnd::Cam_Draw()’:
bug201.cc:95609:6: internal compiler error: in set_lattice_value, at
tree-ssa-cc
p.c:535
 void CamWnd::Cam_Draw() {
      ^
0xed5857 set_lattice_value
    ../../src/trunk/gcc/tree-ssa-ccp.c:535
0xedacdc visit_assignment
    ../../src/trunk/gcc/tree-ssa-ccp.c:2290
0xedacdc ccp_visit_stmt
    ../../src/trunk/gcc/tree-ssa-ccp.c:2364
0xf63174 simulate_stmt
    ../../src/trunk/gcc/tree-ssa-propagate.c:348

This might be related to bug # 63914.
>From gcc-bugs-return-484392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 22 21:29:51 2015
Return-Path: <gcc-bugs-return-484392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68428 invoked by alias); 22 Apr 2015 21:29:50 -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 68367 invoked by uid 48); 22 Apr 2015 21:29:46 -0000
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65837] [arm-linux-gnueabihf] lto1 target specific builtin not available
Date: Wed, 22 Apr 2015 21:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ramana 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-65837-4-St0Ycllo2l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65837-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-04/txt/msg01944.txt.bz2
Content-length: 1390

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

--- Comment #4 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
(In reply to prathamesh3492 from comment #3)
> Hi,
> I tried to reproduce the error with a reduced test-case:
>
> #include "arm_neon.h"
>
> float32x2_t a, b, c, e;
>
> int main()
> {
>   e = __builtin_neon_vmls_lanev2sf (a, b, c, 0);
>   return 0;
> }
>
> arm-linux-gnueabihf-gcc -mfpu=neon test.c -flto test.c -c
> arm-linux-gnueabihf-gcc test.o -flto -o test
> lto1: fatal error: target specific builtin not available
> compilation terminated.

Ofcourse, that's expected behaviour - you don't have support for the SIMD
intrinsics if you don't ask for it on the command line or your compiler doesn't
default to generating code for the SIMD unit.

> lto-wrapper: fatal error:
> /home/prathamesh.kulkarni/gnu-toolchain/gcc-chromium-arm-linux-gnueabihf/
> builds/destdir/x86_64-unknown-linux-gnu/bin/arm-linux-gnueabihf-gcc returned
> 1 exit status
> compilation terminated.
>
> However passing -mfpu=neon for linking works:
> arm-linux-gnueabihf-gcc -mfpu=neon test.o -flto -o test
>
> I suppose similar thing must be happening during linking
> libshared_memory_support.so for chromium build ?
> I couldn't see -mfpu=neon in the command line used for linking
> libshared_memory_support.so

RESOLVED INVALID then ?

regards
Ramana

>
> Thank you
> Prathamesh