Hi,
Jeff Law writes:
> On 5/10/23 19:20, Jiufu Guo wrote:
>>
>> Hi,
>>
>> I would like to ping:
>> https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609396.html
>>
>> We know there are a few issues related to aggregate parameter and
>> returns. I'm thinking if it is ok for trunk to use t
On 5/10/23 19:20, Jiufu Guo wrote:
Hi,
I would like to ping:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609396.html
We know there are a few issues related to aggregate parameter and
returns. I'm thinking if it is ok for trunk to use this patch to
resolve part of those issues.
I
Hi,
I would like to ping:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609396.html
We know there are a few issues related to aggregate parameter and
returns. I'm thinking if it is ok for trunk to use this patch to
resolve part of those issues.
BR,
Jeff (Jiufu)
Jiufu Guo via Gcc-p
Hi,
Gentle ping:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609396.html
Thanks for comments and suggestions!
I'm thinking that we may use these patches to fix some of the issues
on parm and returns.
Sorry for the late ping for this patch to ask if this is acceptable.
BR,
Jeff (Jiu
Hi,
This patch is fixing an issue about parameter accessing if the
parameter is struct type and passed through integer registers, and
there is floating member is accessed. Like below code:
typedef struct DF {double a[4]; long l; } DF;
double foo_df (DF arg){return arg.a[3];}
On ppc64le, with tru
