public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Kazu Hirata <kazu@cs.umass.edu>, gcc-patches@gcc.gnu.org
Subject: Re: add h8sx support to h8300
Date: Thu, 08 Jul 2004 06:08:00 -0000	[thread overview]
Message-ID: <87fz83f456.fsf@redhat.com> (raw)
In-Reply-To: <oru0wjeays.fsf@free.redhat.lsd.ic.unicamp.br> (Alexandre Oliva's message of "07 Jul 2004 18:58:19 -0300")

Alexandre Oliva <aoliva@redhat.com> writes:
> +     - we would like 'D' to be be NO_REGS when the frame pointer isn't
> +       live, but we the frame pointer may turn out to be needed after
> +       we start reload, and then we may have already decided we don't
> +       have a choice, so we can't do that.  Forcing the register
> +       allocator to use er6 if possible might produce better code for
> +       small functions: it's more efficient to save and restore er6 in
> +       the prologue & epilogue than to do it in a define_split.
> +       Hopefully disparaging 'D' will have a similar effect, without
> +       forcing a reload failure if the frame pointer is found to be
> +       needed too late.  */

Not sure I understand this.  Do you have a testcase?

Richard

  reply	other threads:[~2004-07-08  5:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 14:24 Alexandre Oliva
2004-06-21 17:12 ` Kazu Hirata
2004-06-23  2:23   ` Alexandre Oliva
2004-07-07 22:11   ` Alexandre Oliva
2004-07-08  6:08     ` Richard Sandiford [this message]
2004-07-08  7:41       ` Alexandre Oliva
2004-07-08  9:39         ` Richard Sandiford
2004-07-08 18:16           ` Alexandre Oliva
2004-07-08 18:16             ` Richard Sandiford
2004-07-08 20:23               ` Alexandre Oliva
2004-07-12 20:14                 ` Richard Sandiford
2004-07-14 12:49                   ` Alexandre Oliva
2004-07-14 17:16                     ` Richard Sandiford
2004-07-15  4:11                       ` Alexandre Oliva
2004-07-15  5:22                         ` Richard Sandiford
2004-07-15 16:25                           ` Alexandre Oliva
2004-07-15 17:14                             ` Richard Sandiford
2004-07-15 17:25                               ` Richard Sandiford
2004-07-15 22:23                                 ` Alexandre Oliva
2004-07-08 21:20               ` Alexandre Oliva
2004-07-06 20:56 ` Alexandre Oliva
2004-07-07  2:37 ` Richard Henderson
2004-07-07  7:06   ` Alexandre Oliva
2004-07-07  9:06     ` Richard Henderson
2004-07-08  0:14       ` Alexandre Oliva
2004-07-08  1:22         ` Richard Henderson
2004-07-08  1:26           ` Alexandre Oliva
2004-07-08  2:01             ` Richard Henderson
2004-07-08  4:39               ` Alexandre Oliva
2004-07-08 18:59               ` Alexandre Oliva
2004-07-07  9:13     ` Joseph S. Myers
2004-07-07 19:44       ` Alexandre Oliva

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=87fz83f456.fsf@redhat.com \
    --to=rsandifo@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kazu@cs.umass.edu \
    /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).