From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-444529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28869 invoked by alias); 21 Feb 2014 19:16:51 -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
Received: (qmail 28436 invoked by uid 48); 21 Feb 2014 19:16:47 -0000
From: "meadori at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58595] internal compiler error: in gen_movsi when compiling on arm some files of lttng-tools with -fPIE
Date: Fri, 21 Feb 2014 19:16: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: 4.8.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meadori at codesourcery dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58595-4-3AheGyVDUF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58595-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58595-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: 2014-02/txt/msg02286.txt.bz2

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

--- Comment #3 from Meador Inge <meadori at codesourcery dot com> ---
As shown in the backtrace, the ICE occurs when GCSE tries generate a move.
The the following asserts fire in 'gen_movsi':

  gcc_assert (GET_CODE (tmp) == SYMBOL_REF);                                
  gcc_assert (SYMBOL_REF_TLS_MODEL (tmp) != 0);

This is because the move operands look like:

  (gdb) p debug_rtx(operands[0])
  (reg/f:SI 115)

  (gdb) p debug_rtx(operands[1])
  (mem/u/c:SI (plus:SI (reg:SI 111)
          (unspec:SI [
                  (symbol_ref:SI ("state") [flags 0x90] <var_decl 0xf7c50114
state>)
              ] UNSPEC_PIC_SYM)) [0  S4 A32])

We aren't expecting the 'mem' expression with the TLS reference in side.

I am not sure if this is just an overzealous assert or we have a deeper
issue.  Removing the asserts does allow the code to compile.