[Bug c++/65409] New: ICE in store_field

["bugs at qult dot net" <gcc-bugzilla@gcc.gnu.org>]

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

            Bug ID: 65409
           Summary: ICE in store_field
           Product: gcc
           Version: 4.9.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bugs at qult dot net

Created attachment 35022
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35022&action=edit
ICE-triggering source.

I get an ICE with the attached source, from version 4.8 on to the head of the
Git repository.

Output of Git's cc1plus:

 Foo::Foo() Foo::Foo() Foo::Foo() Bar<T>::Bar(U) Bar<T>::Bar(U) [with U = Foo;
T = Foo] Bar<T>::Bar(U) [with U = Foo; T = Foo] Bar<T>::Bar(U) [with U = Foo; T
= Foo] void __static_initialization_and_destruction_0(int, int) void
_GLOBAL__sub_I_a()
Analyzing compilation unit
Performing interprocedural optimizations
 <*free_lang_data> <visibility> <build_ssa_passes> <chkp_passes>
<opt_local_passes> <free-inline-summary> <whole-program> <inline>Assembling
functions:
 Foo::Foo() Bar<T>::Bar(U) [with U = Foo; T = Foo]
<stdin>: In constructor ‘Bar<T>::Bar(U) [with U = Foo; T = Foo]’:
<stdin>:14:27: internal compiler error: in store_field, at expr.c:6660
0x9cf46f store_field
    ../../gcc/expr.c:6659
0x9d4d10 expand_assignment(tree_node*, tree_node*, bool)
    ../../gcc/expr.c:5000
0x8d5dee expand_call_stmt
    ../../gcc/cfgexpand.c:2388
0x8d5dee expand_gimple_stmt_1
    ../../gcc/cfgexpand.c:3334
0x8d5dee expand_gimple_stmt
    ../../gcc/cfgexpand.c:3488
0x8dc118 expand_gimple_basic_block
    ../../gcc/cfgexpand.c:5500
0x8dd9f7 execute
    ../../gcc/cfgexpand.c:6118

When uncommenting the commented-out fourth attribute of Foo, the ICE goes away.
>From gcc-bugs-return-480225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Mar 12 18:33:01 2015
Return-Path: <gcc-bugs-return-480225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34463 invoked by alias); 12 Mar 2015 18:33:01 -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 34392 invoked by uid 48); 12 Mar 2015 18:32:56 -0000
From: "boger at us dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/64999] s390x libgo test failure in TestMemoryProfiler
Date: Thu, 12 Mar 2015 18:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boger at us dot ibm.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64999-4-9Wh2wawEOA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64999-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64999-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-03/txt/msg01369.txt.bz2
Content-length: 814

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

--- Comment #53 from boger at us dot ibm.com ---
I was taking the approach of only fixing what was known to be broken, and I was
not aware that this was broken on other platforms.  Minimizing risk.  I can
change it for all platforms but these tests are not broken on x86 today with
the pc decremented in both libbacktrace and in pprof.go and I don't understand
why not so I didn't want to mess with it.

I'm not sure if I understand how it would work to add an argument to callback.
The call to callback happens much later after the ip_before_insn flag has been
set:  from inside unwind -> backtrace_pcinfo -> dwarf_fileline ->
dwarf_lookup_pc -> callback.  Do you mean pass this flag as an argument to each
of these functions so it can be passed to callback?