From: Alan Modra <amodra@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: Jeff Law <law@redhat.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Jan Hubicka <hubicka@ucw.cz>, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [PATCH] calls.c:can_implement_as_sibling_call_p REG_PARM_STACK_SPACE check
Date: Fri, 2 Oct 2020 17:03:50 +0930 [thread overview]
Message-ID: <20201002073350.GR15011@bubble.grove.modra.org> (raw)
In-Reply-To: <20201002071105.GP15011@bubble.grove.modra.org>
On Fri, Oct 02, 2020 at 04:41:05PM +0930, Alan Modra wrote:
> This moves an #ifdef block of code from calls.c to
> targetm.function_ok_for_sibcall.
Not only did I miss cc'ing the i386 maintainers, I missed seeing that
the ATTRIBUTE_UNUSED reg_parm_stack_space param of
can_implement_as_sibling_call_p is now always unused. Please consider
that parameter removed.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-10-02 7:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 7:11 Alan Modra
2020-10-02 7:33 ` Alan Modra [this message]
2020-10-12 12:07 ` Alan Modra
2020-10-22 11:12 ` Alan Modra
2020-10-02 18:50 ` Segher Boessenkool
2020-10-04 12:39 ` Alan Modra
2020-10-05 15:12 ` Segher Boessenkool
2020-10-30 9:21 ` Richard Sandiford
2020-10-30 13:40 ` Alan Modra
2020-11-02 9:46 ` [PATCH 1/2] can_implement_as_sibling_call_p REG_PARM_STACK_SPACE check V2 Alan Modra
2020-11-02 9:49 ` [PATCH 2/2] [RS6000] " Alan Modra
2020-11-02 21:17 ` Segher Boessenkool
2020-11-02 14:34 ` [PATCH 1/2] can_implement_as_sibling_call_p " Richard Sandiford
2020-11-02 21:14 ` Segher Boessenkool
2020-11-02 14:27 ` [PATCH] calls.c:can_implement_as_sibling_call_p REG_PARM_STACK_SPACE check Richard Sandiford
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=20201002073350.GR15011@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=ubizjak@gmail.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).