public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Jan Hubicka <jh@suse.cz>
Cc: Fergus Henderson <fjh@cs.mu.oz.au>, <gcc-patches@gcc.gnu.org>
Subject: Re: [3.4-BIB] x86-64 sibcall fixes try III
Date: Mon, 28 Oct 2002 03:13:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0210281209530.20702-100000@wotan.suse.de> (raw)
In-Reply-To: <20021028105708.GD26101@kam.mff.cuni.cz>

Hi,

On Mon, 28 Oct 2002, Jan Hubicka wrote:

> > >
> > > IMHO it would be much nicer to name those CALL_USED_REGS and
> > > CALL_USED_64_REGS.
> >
> > I would even suggest CALL_CLOBBERED... The term call-used is misleading,
> > it only can be justified with gcc's history of having it named such since
> > ages (and wrongly so IMO).  The term "use" doesn't indicate at all that
> > all those registers can be changed after a call.
> >
> > Besides from that, I also don't exactly like the addition of more register
> > classes.
>
> Any idea for good sollution without them?

Unfortunately no ;-(  You could prohibit sibcalls with too many arguments,
but that's not necessarily a good solution ;)

> One I got today is to simply encode hard register for this (ie always
> use r11). Also not perfect.

What would this affect?  Only sibcall with many arguments?  If yes, then
this would be a better solution IMHO.


Ciao,
Michael.

  reply	other threads:[~2002-10-28 11:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 10:58 [3.4-BIB] x86-64 sibcall fixes Jan Hubicka
2002-10-15 12:41 ` Michael Matz
2002-10-15 12:44   ` Jan Hubicka
2002-10-15 13:45 ` Richard Henderson
2002-10-27 11:32   ` Jan Hubicka
2002-10-27 12:59     ` Jan Hubicka
2002-10-27 13:16       ` [3.4-BIB] x86-64 sibcall fixes try III Jan Hubicka
2002-10-27 13:44         ` Jakub Jelinek
2002-10-27 13:57           ` Jan Hubicka
2002-10-29  5:43             ` Richard Henderson
2002-10-29  5:48               ` Jan Hubicka
2002-10-27 14:46         ` Andreas Bauer
2002-10-27 17:41         ` Fergus Henderson
2002-10-28  2:51           ` Jan Hubicka
2002-10-28  2:53           ` Michael Matz
2002-10-28  2:57             ` Jan Hubicka
2002-10-28  3:13               ` Michael Matz [this message]
2002-10-28  4:25                 ` Jan Hubicka
2002-10-28  6:26                   ` [3.4-BIB] x86-64 sibcall fixes try IV Jan Hubicka
2002-10-28 19:32                     ` Fergus Henderson
2002-10-29  7:51                     ` Richard Henderson
2002-10-29  5:43     ` [3.4-BIB] x86-64 sibcall fixes Richard Henderson
2002-10-29  5:45       ` Jan Hubicka
2002-10-20 19:54 ` Andreas Bauer

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=Pine.LNX.4.33.0210281209530.20702-100000@wotan.suse.de \
    --to=matz@suse.de \
    --cc=fjh@cs.mu.oz.au \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jh@suse.cz \
    /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).