public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63347] [5 regression] m68k misoptimisation with -fschedule-insns
Date: Wed, 11 Feb 2015 18:51:00 -0000 [thread overview]
Message-ID: <bug-63347-4-8Kq0ndkIZ8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63347-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bernds at codesourcery dot com |law at redhat dot com
--- Comment #14 from Jeffrey A. Law <law at redhat dot com> ---
I think we can fix this by just queueing the SCHED_GROUP_P insn for a single
cycle rather than for its full cost from within prune_ready_list. That will
cause us to reexamine the ready list each cycle. If some non-SCHED_GROUP_P
becomes ready before the SCHED_GROUP_P insn is ready, then the
non-SCHED_GROUP_P insn will go back to the queue because it's not part of the
scheduling group. Which is exactly what we want.
I'm testing with that fix now.
next prev parent reply other threads:[~2015-02-11 18:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-63347-4@http.gcc.gnu.org/bugzilla/>
2014-09-23 22:07 ` [Bug target/63347] " schwab@linux-m68k.org
2014-09-26 18:39 ` jifl-bugzilla at jifvik dot org
2014-10-04 19:27 ` mikpelinux at gmail dot com
2014-10-06 22:10 ` mikpelinux at gmail dot com
2014-10-10 15:41 ` schwab@linux-m68k.org
2014-12-09 5:09 ` jifl-bugzilla at jifvik dot org
2014-12-09 8:44 ` schwab@linux-m68k.org
2014-12-15 21:07 ` mikpelinux at gmail dot com
2015-01-19 22:30 ` law at redhat dot com
2015-02-09 12:46 ` [Bug target/63347] [5 regression] " bernds at gcc dot gnu.org
2015-02-09 20:57 ` law at redhat dot com
2015-02-10 13:32 ` bernds at gcc dot gnu.org
2015-02-11 18:51 ` law at redhat dot com [this message]
2015-02-11 23:29 ` law at gcc dot gnu.org
2015-02-12 5:07 ` [Bug target/63347] [4.9 " law at redhat dot com
2015-02-12 5:14 ` law at redhat dot com
2015-03-13 10:08 ` rguenth at gcc dot gnu.org
2015-06-26 19:53 ` jakub at gcc dot gnu.org
2015-06-26 20:27 ` 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-63347-4-8Kq0ndkIZ8@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).