public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: guojiufu <guojiufu@linux.ibm.com>
To: Jeff Law <jeffreyalaw@gmail.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: Thu, 04 May 2023 13:49:38 +0800	[thread overview]
Message-ID: <df7d9c5baccfa75623b5729adbdd36e4@linux.ibm.com> (raw)
In-Reply-To: <0221bead-5d08-cb56-e620-642825c1abc3@gmail.com>

Hi,

On 2023-05-01 03:00, Jeff Law wrote:
> On 3/16/23 21:39, Jiufu Guo wrote:
>> Hi,
>> 
>> When assigning a parameter to a variable, or assigning a variable to
>> return value with struct type, and the parameter/return is passed
>> through registers.
>> For this kind of case, it would be better to use the nature mode of
>> the registers to move the content for the assignment.
>> 
>> As the example code (like code in PR65421):
>> 
>> typedef struct SA {double a[3];} A;
>> A ret_arg_pt (A *a) {return *a;} // on ppc64le, expect only 3 lfd(s)
>> A ret_arg (A a) {return a;} // just empty fun body
>> void st_arg (A a, A *p) {*p = a;} //only 3 stfd(s)
>> 
>> Comparing with previous version:
>> https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609394.html
>> This version refine code to eliminated reductant code in  the sub
>> routine "move_sub_blocks".
>> 
>> Bootstrap and regtest pass on ppc64{,le}.
>> Is this ok for trunk?
>> 
...

>> diff --git a/gcc/expr.cc b/gcc/expr.cc
>> index 15be1c8db99..97a7be9542e 100644
>> --- a/gcc/expr.cc
>> +++ b/gcc/expr.cc
>> @@ -5559,6 +5559,41 @@ mem_ref_refers_to_non_mem_p (tree ref)
>>     return non_mem_decl_p (base);
>>   }
>>   +/* Sub routine of expand_assignment, invoked when assigning from a
>> +   parameter or assigning to a return val on struct type which may
>> +   be passed through registers.  The mode of register is used to
>> +   move the content for the assignment.
>> +
>> +   This routine generates code for expression FROM which is BLKmode,
>> +   and move the generated content to TO_RTX by su-blocks in SUB_MODE. 
>>  */
>> +
>> +static void
>> +move_sub_blocks (rtx to_rtx, tree from, machine_mode sub_mode)
>> +{
>> +  gcc_assert (MEM_P (to_rtx));
>> +
>> +  HOST_WIDE_INT size = MEM_SIZE (to_rtx).to_constant ();
> Consider the case of a BLKmode return value.  Isn't TO_RTX in this
> case a BLKmode object?

Thanks for this question!

Yes, the mode of TO_RTX is BLKmode.
As we know, when the function returns via registers, the mode of
the `return-rtx` could also be BLKmode.  This patch is going to
improve these kinds of cases.

For example:
```
typedef struct FLOATS
{
   double a[3];
} FLOATS;
FLOATS ret_arg_pt (FLOATS *a){return *a;}
```

D.3952 = *a_2(D); //this patch enhance this assignment
return D.3952;

The mode is BLKmode for the rtx of `D.3952` is BLKmode, and the
rtx for "DECL_RESULT(current_function_decl)".  And the DECL_RESULT
represents the return registers.

BR,
Jeff (Jiufu)
> 
> It looks pretty good at this point.
> 
> jeff

  reply	other threads:[~2023-05-04  5:49 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 [this message]
2023-05-05 23:37     ` Jeff Law
2023-05-09 13:43       ` Jiufu Guo
2023-06-04 16:59         ` Jeff Law
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=df7d9c5baccfa75623b5729adbdd36e4@linux.ibm.com \
    --to=guojiufu@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.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).