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 middle-end/59743] [4.9 Regression] ICE: Segmentation fault
Date: Thu, 09 Jan 2014 23:45:00 -0000 [thread overview]
Message-ID: <bug-59743-4-M7LhwXjeVZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59743-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59743
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #5)
> I think we can just check DF_INSN_LUIDs here to catch this case. My systems
> are busy right now, but I should be able to nail this down as soon as one
> frees up.
But is DF_INSN_LUID always computed? I mean, for -O2 it probably is, but what
about -O -free ? For -O I think the live problem isn't on and thus I think
DF_INSN_LUID isn't computed. The DF documentation is unfortunately
non-existent :(.
next prev parent reply other threads:[~2014-01-09 23:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 20:41 [Bug rtl-optimization/59743] New: " trippels at gcc dot gnu.org
2014-01-09 21:05 ` [Bug middle-end/59743] " trippels at gcc dot gnu.org
2014-01-09 21:15 ` jakub at gcc dot gnu.org
2014-01-09 21:20 ` law at redhat dot com
2014-01-09 21:50 ` law at redhat dot com
2014-01-09 21:57 ` law at redhat dot com
2014-01-09 22:00 ` trippels at gcc dot gnu.org
2014-01-09 23:45 ` jakub at gcc dot gnu.org [this message]
2014-01-10 5:21 ` law at redhat dot com
2014-01-10 5:34 ` law at redhat dot com
2014-01-10 21:48 ` law at redhat dot com
2014-01-10 22:13 ` law at gcc dot gnu.org
2014-01-10 22:14 ` law at redhat dot com
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-59743-4-M7LhwXjeVZ@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).