public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57662] [4.9 Regression] ICE: SIGSEGV in code_motion_process_successors with -fschedule-insns2 -fselective-scheduling2
Date: Thu, 31 Oct 2013 06:05:00 -0000 [thread overview]
Message-ID: <bug-57662-4-qW49cZbJpo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57662-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57662
--- Comment #6 from Andrey Belevantsev <abel at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> Fixed according to
>
> 2013-08-14 Andrey Belevantsev <abel@ispras.ru>
>
> PR rtl-optimization/57662
> * sel-sched.c (code_motion_process_successors): When the current insn
> is removed after the recursive traversal, break from the loop.
> Add comments and debug printouts.
>
> (?)
Yes. Sorry, I keep forgetting that the post-commit Bugzilla autoupdate no
longer works so I didn't look at the PR after committing.
next prev parent reply other threads:[~2013-10-31 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 13:49 [Bug rtl-optimization/57662] New: " zsojka at seznam dot cz
2013-06-24 11:05 ` [Bug rtl-optimization/57662] " rguenth at gcc dot gnu.org
2013-07-24 10:18 ` mpolacek at gcc dot gnu.org
2013-07-24 14:25 ` mpolacek at gcc dot gnu.org
2013-08-13 13:08 ` abel at gcc dot gnu.org
2013-08-14 6:32 ` abel at gcc dot gnu.org
2013-10-30 12:57 ` rguenth at gcc dot gnu.org
2013-10-31 6:05 ` abel at gcc dot gnu.org [this message]
2014-02-03 12:01 ` abel 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-57662-4-qW49cZbJpo@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).