on 2024/5/29 14:32, Alexandre Oliva wrote:
> On May 26, 2024, "Kewen.Lin" wrote:
>
>> Hi,
>> on 2024/4/22 17:38, Alexandre Oliva wrote:
>>> Ping?
>>> https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566530.html
>>> (modified version follows)
>
>> Segher originated this test case, I was expec
On May 26, 2024, "Kewen.Lin" wrote:
> Hi,
> on 2024/4/22 17:38, Alexandre Oliva wrote:
>> Ping?
>> https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566530.html
>> (modified version follows)
> Segher originated this test case, I was expecting he can chime in this. :)
Me too ;-)
>> We've obs
Hi,
on 2024/4/22 17:38, Alexandre Oliva wrote:
> Ping?
> https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566530.html
> (modified version follows)
Segher originated this test case, I was expecting he can chime in this. :)
>
>
> We've observed failures of this test on powerpc configurations
On Apr 22, 2024, Alexandre Oliva wrote:
> for gcc/testsuite/ChangeLog
> * gcc.target/powerpc/pr88233.c: Make some alignment strictness
> and calling conventions assumptions explicit. Restore uniform
> codegen expectations
Ping? https://gcc.gnu.org/pipermail/gcc-patches/2024
Ping?
https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566530.html
(modified version follows)
We've observed failures of this test on powerpc configurations that
default to different calling conventions and alignment requirements.
Both settings are needed for the original expectations to be m
We've observed failures of this test on powerpc configurations that
default to different calling conventions and alignment requirements.
Both settings are needed for the expectations to be met.
This was regstrapped on x86_64-linux-gnu and ppc64-linux-gnu, and tested
with a cross to a ppc64-vxwor
