public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: "Michael S. Zick" <mszick@goquest.com>
Cc: Andy Walker <ja_walker@earthlink.net>,
	"GCC Developer's List" <gcc@gcc.gnu.org>
Subject: Re: An unusual Performance approach using Synthetic registers, and a request for guidance.
Date: Sat, 28 Dec 2002 04:58:00 -0000	[thread overview]
Message-ID: <orhecyairg.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <02122710093100.00766@localhost.localdomain>

On Dec 27, 2002, "Michael S. Zick" <mszick@goquest.com> wrote:

> So, I think (personal opinion here), using the %EBX register as the base 
> (frame pointer) of the synthetic register frames should be your first choice.

'cept %EBX is used as the PIC base register, and you can't really
remap that to a virtual register unless you change PLT entries.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

  parent reply	other threads:[~2002-12-28  4:07 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 [this message]
2002-12-28  9:43     ` Michael S. Zick
2002-12-29  5:33       ` Andy Walker
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=orhecyairg.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ja_walker@earthlink.net \
    --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).