public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65771] [5 Regression] ICE (in loc_list_from_tree, at dwarf2out.c:14964) on arm-linux-gnueabihf
Date: Thu, 16 Apr 2015 14:24:00 -0000	[thread overview]
Message-ID: <bug-65771-4-hyOP9Otz5N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65771-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|arm-linux-gnueabihf         |

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Happens on x86_64-linux too, started with r214899.

So, at *.optimized we have:
  # DEBUG D#2 => b
  # DEBUG D#1 => a[D#2].t
  # DEBUG c => D#1
which is expanded as:
(debug_insn 5 2 6 2 (var_location:SI D#2 (mem/c:SI (symbol_ref:SI ("b") [flags
0x82]  <var_decl 0x7f8953872990 b>) [0 b+0 S4 A32])) pr65771.c:8 -1
     (nil))
(debug_insn 6 5 7 2 (var_location:SI D#1 (mem/j:SI (plus:SI (ashift:SI
(debug_expr:SI D#2)
                (const_int 3 [0x3]))
            (const:SI (plus:SI (symbol_ref:SI ("a") [flags 0xaa]  <var_decl
0x7f8953872900 a>)
                    (const_int 4 [0x4])))) [0 a[D#2].t+0 S4 A32])) pr65771.c:8
-1
     (nil))
(debug_insn 7 6 0 2 (var_location:SI c (debug_expr:SI D#1)) pr65771.c:8 -1
     (nil))
and vartracking makes:
(note 15 2 14 2 (var_location c (mem/j:SI (plus:SI (ashift:SI (mem/c:SI
(symbol_ref:SI ("b") [flags 0x82]  <var_decl 0x7f8953872990 b>) [0 b+0 S4 A
32])
            (const_int 3 [0x3]))
        (const:SI (plus:SI (symbol_ref:SI ("a") [flags 0xaa]  <var_decl
0x7f8953872900 a>)
                (const_int 4 [0x4])))) [0 a[D#2].t+0 S4 A32]))
NOTE_INSN_VAR_LOCATION)
out of this.  Var-tracking for obvious reasons can only replace the
DEBUG_EXPR_DECLs when they appear in debug_expr RTL, because we track
DEBUG_EXPR_DECL values at RTL as RTL expressions, rather than tree.  The
problem is I believe that we try to use the MEM_EXPR as a fallback and if it
contains DEBUG_EXPR_DECL, dwarf2out.c is upset.


  parent reply	other threads:[~2015-04-16 14:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 13:22 [Bug target/65771] New: " doko at gcc dot gnu.org
2015-04-15 13:24 ` [Bug target/65771] " ktkachov at gcc dot gnu.org
2015-04-15 13:29 ` ktkachov at gcc dot gnu.org
2015-04-15 13:34 ` rguenth at gcc dot gnu.org
2015-04-15 13:47 ` ktkachov at gcc dot gnu.org
2015-04-15 13:49 ` ktkachov at gcc dot gnu.org
2015-04-15 14:55 ` ktkachov at gcc dot gnu.org
2015-04-16 14:10 ` jakub at gcc dot gnu.org
2015-04-16 14:24 ` jakub at gcc dot gnu.org [this message]
2015-04-16 14:39 ` [Bug debug/65771] " ktkachov at gcc dot gnu.org
2015-04-16 14:51 ` jakub at gcc dot gnu.org
2015-04-17  7:45 ` [Bug debug/65771] [5/6 " jakub at gcc dot gnu.org
2015-04-17  7:46 ` jakub at gcc dot gnu.org
2015-04-17  7:48 ` [Bug debug/65771] " jakub at gcc dot gnu.org
2015-04-17 14:17 ` jakub at gcc dot gnu.org
2015-04-22 12:02 ` jakub at gcc dot gnu.org
2015-06-25  0:03 ` ramana at gcc dot gnu.org
2015-07-16  9:18 ` rguenth 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-65771-4-hyOP9Otz5N@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).