From: Jeff Law <jeffreyalaw@gmail.com>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de,
segher@kernel.crashing.org, dje.gcc@gmail.com, linkw@gcc.gnu.org,
meissner@linux.ibm.com
Subject: Re: [PATCH V5] Use reg mode to move sub blocks for parameters and returns
Date: Sun, 4 Jun 2023 10:59:09 -0600 [thread overview]
Message-ID: <a61cfd16-0268-b75c-adbc-cb3a0fb84cba@gmail.com> (raw)
In-Reply-To: <7n3545d3hq.fsf@ltcden2-lp1.aus.stglabs.ibm.com>
On 5/9/23 07:43, Jiufu Guo wrote:
> Thanks for point out this! Yes, BLKmode rtx may not always be a MEM.
> MEM_SIZE is only ok for MEM after the it's known size is computed.
> Here MEM_SIZE is fine just because it is an stack rtx corresponding
> to the type of parameter and returns which has been computed.
>
> I updated the patch to resolve the conflicts with the trunk, and
> retest bootstrap&testsuite, and then updated the patch a new version.
>
> And this version pass bootstrap and regtest on ppc64{,le}, x86_64.
>
> The major change is 'move_sub_blocks' only handles the case when
> the block size can be move by same submode, or say (size % sub_size)
> is 0. If no objection, I would committed the new version.
>
> BR,
> Jeff (Jiufu)
>
> gcc/ChangeLog:
>
> * cfgexpand.cc (expand_used_vars): Update to mark DECL_USEDBY_RETURN_P
> for returns.
> * expr.cc (move_sub_blocks): New function.
> (expand_assignment): Update assignment code about returns/parameters.
> * function.cc (assign_parm_setup_block): Update to mark
> DECL_REGS_TO_STACK_P for parameter.
> * tree-core.h (struct tree_decl_common): Add comment.
> * tree.h (DECL_USEDBY_RETURN_P): New define.
> (DECL_REGS_TO_STACK_P): New define.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/powerpc/pr65421-1.c: New test.
> * gcc.target/powerpc/pr65421-2.c: New test.
I don't think this was ever explicitly ACK'd. OK for the trunk.
jeff
next prev parent reply other threads:[~2023-06-04 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 3:39 Jiufu Guo
2023-04-30 19:00 ` Jeff Law
2023-05-04 5:49 ` guojiufu
2023-05-05 23:37 ` Jeff Law
2023-05-09 13:43 ` Jiufu Guo
2023-06-04 16:59 ` Jeff Law [this message]
2023-06-07 1:21 ` guojiufu
2023-05-01 15:52 ` Segher Boessenkool
2023-05-04 5:55 ` guojiufu
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=a61cfd16-0268-b75c-adbc-cb3a0fb84cba@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=linkw@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.org \
/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).