From: Jeffrey A Law <law@hurl.cygnus.com>
To: Bernd Schmidt <crux@Pool.Informatik.RWTH-Aachen.DE>
Cc: egcs@cygnus.com
Subject: Re: Some Haifa scheduler bugs
Date: Mon, 01 Sep 1997 20:42:00 -0000 [thread overview]
Message-ID: <14105.873171711@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.90.970826141030.2901K-100000@maigret.informatik.rwth-aachen.de>
> I think you won't get the right return value. You want to return the
> last insn in a SCHED_GROUP or a note that was placed after it.
> I had my reasons to use two loops ;)
You're right. Seems to me that the return value for move_insn should
always be the return value from the first call to reemit_notes. Correct?
In which case it's pretty simple to record the return value from
the first call to reemit_notes.
And I don't doubt you had good reasons to use two loops; I just want
to make absolutely sure I understand the problem. Handling of notes
and SCHED_GROUP_P insns have both been particularly difficult areas
of the scheduler to implement correctly.
> The whole affair with SCHED_GROUP_P is extremely messy.
Agreed.
> How about using extra data structures that describe which insns
> to schedule together, which notes to put before them, and the
> dependencies between them.
I'm all for it.
> scheduled together with an insn might make the code clearer. I think it
> would fit in better with the fact that Haifa schedules forward. I didn't
> try it, though; maybe there are problems with that approach, too.
Well, haifa does both forward and backward analysis -- so it might
just move the problematical code elsewhere in the scheduler.
jeff
next parent reply other threads:[~1997-09-01 20:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.3.90.970826141030.2901K-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:42 ` Jeffrey A Law [this message]
1997-09-04 11:27 meissner
[not found] <Pine.SOL.3.90.970826140826.2901J-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:33 ` Jeffrey A Law
1997-09-03 9:30 ` Bernd Schmidt
1997-09-03 9:37 ` Jeffrey A Law
1997-09-03 9:44 ` Bernd Schmidt
1997-09-03 10:07 ` Jeffrey A Law
1997-09-05 7:15 ` Bernd Schmidt
1997-09-05 7:55 ` Jeffrey A Law
1997-09-05 8:33 ` Ian Lance Taylor
1997-09-03 11:58 ` Jim Wilson
1997-09-03 11:39 ` Paul Koning
1997-09-03 11:50 ` David Edelsohn
1997-09-03 13:13 ` Richard Henderson
1997-09-03 13:19 ` Jeffrey A Law
1997-09-04 9:33 ` Craig Burley
1997-09-04 11:12 ` Jeffrey A Law
1997-09-04 11:33 ` David S. Miller
1997-09-04 14:38 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
1997-08-26 14:34 Bernd Schmidt
1997-08-22 13:53 Building of generated parser files Andreas Schwab
1997-08-22 15:02 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-22 15:24 ` Jeffrey A Law
1997-08-22 10:48 Building of generated parser files Niklas Hallqvist
1997-08-22 13:28 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-21 16:51 Problems on PowerPC David Edelsohn
1997-08-21 17:43 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-21 15:20 egcs repository Joel Sherrill
1997-08-21 15:47 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-19 19:00 Jeffrey A Law
1997-08-19 17:54 Jeffrey A Law
1997-08-19 7:36 egcs: A new compiler project to merge the existing GCC forks (fwd) Robert Wilhelm
1997-08-19 9:34 ` Some Haifa scheduler bugs Bernd Schmidt
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=14105.873171711@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=crux@Pool.Informatik.RWTH-Aachen.DE \
--cc=egcs@cygnus.com \
/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).