public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: "Takayuki 'January June' Suwa" <jjsuwa_sys3175@yahoo.co.jp>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] xtensa: Improve indirect sibling call handling
Date: Thu, 18 Aug 2022 13:01:06 -0700	[thread overview]
Message-ID: <CAMo8Bf+ciL3dJtv40d=O6LsPu_hXvXs_zj4WUwSMAMPWsYATeg@mail.gmail.com> (raw)
In-Reply-To: <20e955d6-d517-c20a-605a-34082189e9ca@yahoo.co.jp>

On Thu, Aug 18, 2022 at 3:06 AM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
> No longer needs the dedicated hard register (A11) for the address of the
> call and the split patterns for fixups, due to the introduction of appropriate
> register class and constraint.
>
> (Note: "ISC_REGS" contains a hard register A8 used as a "static chain"
>  pointer for nested functions, but no problem;  Pointer to nested function
>  actually points to "trampoline", and trampoline itself doesn't receive
>  "static chain" pointer to its parent's stack frame from the caller.)
>
> gcc/ChangeLog:
>
>         * config/xtensa/xtensa.h
>         (enum reg_class, REG_CLASS_NAMES, REG_CLASS_CONTENTS):
>         Add new register class "ISC_REGS".
>         * config/xtensa/constraints.md (c): Add new register constraint.
>         * config/xtensa/xtensa.md (define_constants): Remove "A11_REG".
>         (sibcall_internal, sibcall_value_internal):
>         Change to use the new register constraint, and remove two split
>         patterns for fixups that are no longer needed.
>
> gcc/testsuite/ChangeLog:
>
>         * gcc.target/xtensa/sibcalls.c: Add a new test function to ensure
>         that registers for arguments (occupy from A2 to A7) and for indirect
>         sibcall (should be assigned to A8) neither conflict nor spill out.
> ---
>  gcc/config/xtensa/constraints.md           |  5 ++++
>  gcc/config/xtensa/xtensa.h                 |  3 +++
>  gcc/config/xtensa/xtensa.md                | 29 ++--------------------
>  gcc/testsuite/gcc.target/xtensa/sibcalls.c |  5 ++++
>  4 files changed, 15 insertions(+), 27 deletions(-)

Regtested for target=xtensa-linux-uclibc, no new regressions.
Committed to master.

-- 
Thanks.
-- Max

      reply	other threads:[~2022-08-18 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 10:03 Takayuki 'January June' Suwa
2022-08-18 20:01 ` Max Filippov [this message]

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='CAMo8Bf+ciL3dJtv40d=O6LsPu_hXvXs_zj4WUwSMAMPWsYATeg@mail.gmail.com' \
    --to=jcmvbkbc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jjsuwa_sys3175@yahoo.co.jp \
    /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).