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 debug/65549] [5 Regression] crash in htab_hash_string with -flto -g
Date: Mon, 30 Mar 2015 17:28:00 -0000	[thread overview]
Message-ID: <bug-65549-4-BTvINCt2Mq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65549-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #6)
> Btw, I always wondered why dwarf2out.c doesn't create such stubs itself when
> it requires a parent (via force_decl_die).

Most probably because dwarf2out.c has never been written with the current state
of LTO in mind, it assumes the FE or the middle-end gives it sane and complete
trees of everything needed.
With early debug info, if done right for LTO, supposedly the problems goes away
again, so either we add some hack for this and accept there are hundreds of
other ways how to get it crashed with -flto -g (perhaps regression on some
particular testcase, but generally all gcc versions with -flto -g contained
lots of various ICEs), or just add this to other cases which show -flto -g is
unsupportable until early debug info is added to GCC 6.


  parent reply	other threads:[~2015-03-30 15:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65549-4@http.gcc.gnu.org/bugzilla/>
2015-03-25 12:08 ` [Bug debug/65549] [5 Regression] crash in htab_hash_string with -flto trippels at gcc dot gnu.org
2015-03-27  8:25 ` trippels at gcc dot gnu.org
2015-03-30 12:05 ` [Bug debug/65549] [5 Regression] crash in htab_hash_string with -flto -g jakub at gcc dot gnu.org
2015-03-30 12:28 ` rguenth at gcc dot gnu.org
2015-03-30 12:30 ` rguenth at gcc dot gnu.org
2015-03-30 17:28 ` jakub at gcc dot gnu.org [this message]
2015-03-31  9:51 ` rguenth at gcc dot gnu.org
2015-03-31 13:06 ` rguenth at gcc dot gnu.org
2015-03-31 13:12 ` rguenth at gcc dot gnu.org
2015-03-31 13:13 ` rguenth at gcc dot gnu.org
2015-03-31 13:16 ` trippels at gcc dot gnu.org
2015-03-31 15:53 ` trippels at gcc dot gnu.org
2015-03-31 16:04 ` trippels at gcc dot gnu.org
2015-03-31 19:52 ` hubicka at gcc dot gnu.org
2015-04-01 12:19 ` jakub at gcc dot gnu.org
2015-04-07 10:07 ` rguenth at gcc dot gnu.org
2015-04-07 10:08 ` [Bug debug/65549] [4.9/5 " rguenth at gcc dot gnu.org
2015-04-07 10:21 ` trippels at gcc dot gnu.org
2015-04-16  9:11 ` [Bug debug/65549] [4.9/5/6 " ferdinandw+gcc at gmail dot com
2015-04-16 10:14 ` ferdinandw+gcc at gmail dot com
2015-04-17  7:58 ` rguenth at gcc dot gnu.org
2015-04-17  8:32 ` rguenth at gcc dot gnu.org
2015-04-17  8:34 ` rguenth at gcc dot gnu.org
2015-04-17  8:38 ` avi@cloudius-systems.com
2015-04-17  8:39 ` rguenth at gcc dot gnu.org
2015-04-17  8:55 ` avi@cloudius-systems.com
2015-04-17 10:15 ` rguenth at gcc dot gnu.org
2015-04-20  7:36 ` rguenther at suse dot de
2015-04-27  9:15 ` ebotcazou at gcc dot gnu.org
2015-06-02 12:33 ` [Bug debug/65549] [4.9/5 " rguenth at gcc dot gnu.org
2015-06-02 12:33 ` [Bug debug/65549] [4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-03  7:39 ` [Bug debug/65549] [4.9 " rguenth at gcc dot gnu.org
2015-06-03 11:04 ` rguenth at gcc dot gnu.org
2015-06-11 13:40 ` rguenth at gcc dot gnu.org
2015-06-11 13:40 ` 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-65549-4-BTvINCt2Mq@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).