public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <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: Tue, 04 Mar 2014 10:15:00 -0000	[thread overview]
Message-ID: <bug-58595-4-HQlhvhGY4a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58595-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from ktkachov at gcc dot gnu.org ---
(In reply to ktkachov from comment #9)
> (In reply to Jakub Jelinek from comment #8)
> > Created attachment 32254 [details]
> > gcc49-pr58595-2.patch
> > 
> > So what about this variant?
> 
> I'll give this a bootstrap and test run, thanks

This patch passes bootstrap but fails regtest:

$SOURCE/gcc/testsuite/gcc.dg/tls/opt-12.c:24:28: internal compiler error: in
arm_legitimize_address, at config/arm/arm.c:7348
0x616d27 arm_legitimize_address
        $SOURCE/gcc/config/arm/arm.c:7348
0x245d17 memory_address_addr_space(machine_mode, rtx_def*, unsigned char)
        $SOURCE/gcc/explow.c:474
0x2576e9 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        $SOURCE/gcc/expr.c:9678
0x2658bd expand_expr
        $SOURCE/gcc/expr.h:455
0x2658bd expand_assignment(tree_node*, tree_node*, bool)
        $SOURCE/gcc/expr.c:5054
0x1bff1f expand_gimple_stmt_1
        $SOURCE/gcc/cfgexpand.c:3214
0x1bff1f expand_gimple_stmt
        $SOURCE/gcc/cfgexpand.c:3310
0x1c13cb expand_gimple_basic_block
        $SOURCE/gcc/cfgexpand.c:5150
0x1c2873 gimple_expand_cfg
        $SOURCE/gcc/cfgexpand.c:5729
0x1c2873 execute
        $SOURCE/gcc/cfgexpand.c:5949
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.

FAIL: gcc.dg/tls/opt-12.c (internal compiler error)

In particular, this assertion fails in arm_legitimize_address:
      gcc_assert (GET_CODE (x) == SYMBOL_REF);


  parent reply	other threads:[~2014-03-04 10:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 19:12 [Bug target/58595] New: " yannick.brosseau at gmail dot com
2013-10-31  9:49 ` [Bug target/58595] " ramana at gcc dot gnu.org
2013-10-31 10:00 ` ramana at gcc dot gnu.org
2014-02-21 19:13 ` meadori at codesourcery dot com
2014-02-21 19:16 ` meadori at codesourcery dot com
2014-03-03 13:40 ` jakub at gcc dot gnu.org
2014-03-03 15:47 ` meadori at codesourcery dot com
2014-03-03 16:00 ` jakub at gcc dot gnu.org
2014-03-03 16:12 ` jakub at gcc dot gnu.org
2014-03-03 16:54 ` jakub at gcc dot gnu.org
2014-03-03 17:16 ` ktkachov at gcc dot gnu.org
2014-03-04 10:15 ` ktkachov at gcc dot gnu.org [this message]
2014-03-04 13:13 ` jakub at gcc dot gnu.org
2014-03-05  8:59 ` ktkachov at gcc dot gnu.org
2014-03-06 12:07 ` jakub at gcc dot gnu.org
2014-04-10  7:46 ` jakub at gcc dot gnu.org
2014-04-10  8:03 ` jakub 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-58595-4-HQlhvhGY4a@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).