public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59440] [4.9 Regression] ICE in force_decl_die, at dwarf2out.c:20111 with -g
Date: Wed, 18 Dec 2013 22:34:00 -0000	[thread overview]
Message-ID: <bug-59440-4-g1eQwUpY4S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59440-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> ---
I see two not so pretty solutions:

a) The simple way: Duplicate debug info by also emitting code for the original
DECL.


b) The hard & slow way:

In tree-nested.c, add another walk_tree(), to be run after walk_function(),
which searches for TREE_CODE() == NAMELIST_DECL.

Then, the easy part follows: Go through the VEC of the NAMELIST_DECL and
replace the original decl by the one returned by
pointer_map_contains(info->var_map, decl).


  parent reply	other threads:[~2013-12-18 22:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 23:03 [Bug fortran/59440] New: " anlauf at gmx dot de
2013-12-10 12:03 ` [Bug fortran/59440] " rguenth at gcc dot gnu.org
2013-12-11 15:05 ` janus at gcc dot gnu.org
2013-12-11 22:29 ` burnus at gcc dot gnu.org
2013-12-11 22:52 ` janus at gcc dot gnu.org
2013-12-12 19:59 ` burnus at gcc dot gnu.org
2013-12-12 22:30 ` anlauf at gmx dot de
2013-12-13  7:26 ` burnus at gcc dot gnu.org
2013-12-18 22:01 ` burnus at gcc dot gnu.org
2013-12-18 22:34 ` burnus at gcc dot gnu.org [this message]
2013-12-19 15:40 ` rguenth at gcc dot gnu.org
2014-01-17  9:24 ` jakub at gcc dot gnu.org
2014-01-17 14:43 ` jakub at gcc dot gnu.org
2014-01-17 14:54 ` jakub at gcc dot gnu.org
2014-01-17 19:52 ` 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-59440-4-g1eQwUpY4S@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).