Hi,
Jeff Law writes:
> On 11/28/22 20:53, Jiufu Guo wrote:
>
>>>
>>> Right, but the number of registers is target dependent, so I don't see
>>> how using "8" or any number of that matter is correct here.
>> I understand. And even for the same struct type, using how many
>> registers to pass a p
On 11/28/22 20:53, Jiufu Guo wrote:
Right, but the number of registers is target dependent, so I don't see
how using "8" or any number of that matter is correct here.
I understand. And even for the same struct type, using how many
registers to pass a parameter, it also dependends on the si
Hi Jeff,
Thanks a lot for your comments!
Jeff Law writes:
> On 11/22/22 19:58, Jiufu Guo wrote:
>> Hi Jeff,
>>
>> Thanks a lot for your comments!
>>
>> Jeff Law writes:
>>
>>> On 11/20/22 20:07, Jiufu Guo wrote:
Jiufu Guo writes:
> Hi,
>
> As mentioned in the previous
On 11/22/22 19:58, Jiufu Guo wrote:
Hi Jeff,
Thanks a lot for your comments!
Jeff Law writes:
On 11/20/22 20:07, Jiufu Guo wrote:
Jiufu Guo writes:
Hi,
As mentioned in the previous version patch:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604646.html
The suboptimal code is
Jiufu Guo via Gcc-patches writes:
> Hi Richard,
>
> Thanks a lot for your comments!
>
> Richard Biener writes:
>
>> On Wed, 23 Nov 2022, Jiufu Guo wrote:
>>
>>> Hi Jeff,
>>>
>>> Thanks a lot for your comments!
>>
>> Sorry for the late response ...
>>
>>> Jeff Law writes:
>>>
>>> > On 11/20/22
Hi Richard,
Thanks a lot for your comments!
Richard Biener writes:
> On Wed, 23 Nov 2022, Jiufu Guo wrote:
>
>> Hi Jeff,
>>
>> Thanks a lot for your comments!
>
> Sorry for the late response ...
>
>> Jeff Law writes:
>>
>> > On 11/20/22 20:07, Jiufu Guo wrote:
>> >> Jiufu Guo writes:
>> >
On Wed, 23 Nov 2022, Jiufu Guo wrote:
> Hi Jeff,
>
> Thanks a lot for your comments!
Sorry for the late response ...
> Jeff Law writes:
>
> > On 11/20/22 20:07, Jiufu Guo wrote:
> >> Jiufu Guo writes:
> >>
> >>> Hi,
> >>>
> >>> As mentioned in the previous version patch:
> >>> https://gcc.gn
Hi Jeff,
Thanks a lot for your comments!
Jeff Law writes:
> On 11/20/22 20:07, Jiufu Guo wrote:
>> Jiufu Guo writes:
>>
>>> Hi,
>>>
>>> As mentioned in the previous version patch:
>>> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604646.html
>>> The suboptimal code is generated for "a
On 11/20/22 20:07, Jiufu Guo wrote:
Jiufu Guo writes:
Hi,
As mentioned in the previous version patch:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604646.html
The suboptimal code is generated for "assigning from parameter" or
"assigning to return value".
This patch enhances the as
Jiufu Guo writes:
> Hi,
>
> As mentioned in the previous version patch:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604646.html
> The suboptimal code is generated for "assigning from parameter" or
> "assigning to return value".
> This patch enhances the assignment from parameters lik
Hi,
As mentioned in the previous version patch:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604646.html
The suboptimal code is generated for "assigning from parameter" or
"assigning to return value".
This patch enhances the assignment from parameters like the below
cases:
/case1.c
t
11 matches
Mail list logo