From: Andy Walker <ja_walker@earthlink.net>
To: Michael S. Zick <mszick@goquest.com>,
Alexandre Oliva <aoliva@redhat.com>
Cc: "GCC Developer's List" <gcc@gcc.gnu.org>
Subject: Re: An unusual Performance approach using Synthetic registers, and a request for guidance.
Date: Sun, 29 Dec 2002 05:33:00 -0000 [thread overview]
Message-ID: <E18SWCC-0007fu-00@grebe.mail.pas.earthlink.net> (raw)
In-Reply-To: <02122807541800.00764@localhost.localdomain>
On Saturday 28 December 2002 07:54 am, Michael S. Zick wrote:
<snip>
> For the general question:
> "If a complex instruction set machine had as many registers as
> a RISC machine, what..."
>
> I see two approachs to investigating this sort of question;
>
> 1) Modify the compiler to support, in general, Synthetic Register Arrays.
> Wherein one could/would butt heads with any and all current design
> decisions for a particular port....
My current approach.
> 2) Do a "new port" to a Synthetic Machine that 99% maps to real hardware,
> leaving the compiler internals untouched.
> You get to make your own design decisions that way and perhaps learn
> if path (1) above is worth doing.
> Mike
If what I am doing gets too complicated, I will keep your suggestion in mind.
The current ix86 machine description file alone has about ten thousand lines
in it. That is a lot to replace.
Andy
next prev parent reply other threads:[~2002-12-29 5:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 5:04 Andy Walker
2002-12-27 10:55 ` Michael S. Zick
2002-12-27 11:44 ` Michael S. Zick
2002-12-28 4:58 ` Alexandre Oliva
2002-12-28 9:43 ` Michael S. Zick
2002-12-29 5:33 ` Andy Walker [this message]
2002-12-29 4:28 ` Andy Walker
2002-12-29 2:18 ` Andy Walker
2002-12-27 6:48 Bonzini
2002-12-27 20:07 ` Dave Hudson
2002-12-29 2:23 ` Andy Walker
2002-12-29 1:57 ` Andy Walker
2002-12-29 6:09 ` Bonzini
2002-12-29 12:04 ` Andy Walker
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=E18SWCC-0007fu-00@grebe.mail.pas.earthlink.net \
--to=ja_walker@earthlink.net \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mszick@goquest.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).