From: Jeffrey A Law <law@upchuck.cygnus.com>
To: Richard Henderson <rth@cygnus.com>
Cc: Jerry Quinn <jquinn@nortelnetworks.com>, egcs@egcs.cygnus.com
Subject: Re: Fwd: Questions on PA machine description?
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <4350.923082138@upchuck> (raw)
Message-ID: <19990430231500.VgYIIfMAEKlsar9UFqDvIBJJdogpG1rTuNEp-rj5JXY@z> (raw)
In-Reply-To: <19990325151052.A28577@cygnus.com>
In message <19990325151052.A28577@cygnus.com>you write:
> On Thu, Mar 25, 1999 at 01:56:39PM -0800, Richard Henderson wrote:
> > The following change seems to do the right thing for Alpha EV5
> > wrt compare+cmove.
>
> The previous patch wouldn't bootstrap the compiler. I goofed on
> stepping through the ready list insns.
I played around a little with this (the patch to get the scheduler to
place dependent insns into the ready list as soon as their depedencies
were resolved) and couldn't ever get the trivial example to fire the
PA equivalent of sethi/lo_sum in the same cycle -- even after hacking up
my pa.md to have an issue/ready delay of zero for ALU insns.
Maybe I'm missing something...
jeff
next prev parent reply other threads:[~1999-04-30 23:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-08 6:49 Jerry Quinn
[not found] ` < 36E3E35A.4BB420BE@americasm01.nt.com >
1999-03-08 20:48 ` Jeffrey A Law
1999-03-09 11:35 ` Jerry Quinn
[not found] ` < 36E577DF.F825BAFB@americasm01.nt.com >
1999-03-09 12:18 ` Jeffrey A Law
1999-03-16 10:49 ` Jerry Quinn
[not found] ` < 36EEA7B6.D3C894DE@americasm01.nt.com >
1999-03-17 20:12 ` Jeffrey A Law
1999-03-18 14:35 ` Jerry Quinn
[not found] ` < 36F17F8C.9FD937FA@americasm01.nt.com >
1999-03-18 21:00 ` Jeffrey A Law
[not found] ` < 18375.921819620@hurl.cygnus.com >
1999-03-19 17:32 ` Richard Henderson
[not found] ` < 19990319173226.C14722@cygnus.com >
1999-03-20 2:08 ` Jeffrey A Law
[not found] ` < 1843.921916006@upchuck >
1999-03-20 10:43 ` Richard Henderson
1999-03-23 14:13 ` Jerry Quinn
[not found] ` < 36F811ED.32912006@americasm01.nt.com >
1999-03-24 1:30 ` Jeffrey A Law
1999-03-24 14:44 ` Jerry Quinn
[not found] ` < 36F96A7D.F0DBDF47@americasm01.nt.com >
1999-03-25 1:01 ` Jeffrey A Law
[not found] ` < 4324.922351870@upchuck >
1999-03-25 13:56 ` Richard Henderson
1999-03-25 15:10 ` Richard Henderson
1999-03-26 10:50 ` Jerry Quinn
1999-03-26 11:04 ` Richard Henderson
1999-03-31 23:46 ` Richard Henderson
1999-03-31 23:46 ` Jerry Quinn
1999-03-26 14:07 ` Jerry Quinn
1999-03-27 16:04 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Jerry Quinn
1999-03-31 23:46 ` Richard Henderson
1999-04-02 11:53 ` Jeffrey A Law [this message]
1999-04-05 15:50 ` Jerry Quinn
1999-04-30 23:15 ` Jerry Quinn
1999-04-30 23:15 ` Jeffrey A Law
1999-03-31 23:46 ` Richard Henderson
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Jerry Quinn
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Jerry Quinn
1999-03-31 23:46 ` Richard Henderson
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Richard Henderson
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Jerry Quinn
1999-03-31 23:46 ` Jeffrey A Law
1999-03-17 20:14 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Jerry Quinn
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Jerry Quinn
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Jerry Quinn
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=4350.923082138@upchuck \
--to=law@upchuck.cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=jquinn@nortelnetworks.com \
--cc=rth@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).