public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael S. Zick <mszick@goquest.com>
To: dewar@gnat.com (Robert Dewar),
	dewar@gnat.com, lord@emf.net, mszick@goquest.com
Cc: gcc@gcc.gnu.org, ja_walker@earthlink.net
Subject: Re: Sythetic registers: modrm/gas question.
Date: Sun, 05 Jan 2003 20:15:00 -0000	[thread overview]
Message-ID: <03010513311000.00808@localhost.localdomain> (raw)
In-Reply-To: <20030105175908.E9176F2DDB@nile.gnat.com>

On Sunday 05 January 2003 11:59 am, Robert Dewar wrote:
> > I have to strongly disagree with that observation.
>
> I am talking very specifically here of the issue of taking register
> renaming into account in register allocation and scheduling algorithms.
> I certainly would be interested in any references you know of in this
> area.
My error, I mis-read the statement.
My mind was somewhere else while my hands were typing.

This entire thread has spured me to dig out my project notes from
a globally optimizing, meta-assembler done about 23 years ago.

I am doing a re-write of the principles and concepts with GCC
in mind. I'll let the list know when I have the draft finished.

If GCC really isn't doing better than a W.A.F.G. in this area,
perhaps it will help.

Mike

  reply	other threads:[~2003-01-05 19:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 18:13 Robert Dewar
2003-01-05 20:15 ` Michael S. Zick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07  3:13 Robert Dewar
2003-01-05 14:24 Robert Dewar
2003-01-05 16:56 ` Michael S. Zick
2003-01-05 17:37   ` Michael S. Zick
2003-01-05 22:33 ` Tom Lord
2003-01-05 13:25 Robert Dewar
2003-01-06  5:36 ` Andy Walker
2003-01-06 19:42 ` Tom Lord
2003-01-05 12:28 Robert Dewar
2003-01-06  5:04 ` Andy Walker
2003-01-06 19:47 ` Tom Lord
2003-01-05  6:08 Andy Walker
2003-01-06 23:54 ` Mike Stump
2003-01-07  6:15   ` 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=03010513311000.00808@localhost.localdomain \
    --to=mszick@goquest.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ja_walker@earthlink.net \
    --cc=lord@emf.net \
    /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).