On Thu, Jun 30, 2022 at 4:17 AM Kito Cheng wrote:
>
> Committed to trunk, thanks :)
>
> Is it OK for gcc-11 and gcc-12 branches?
Yes, if the same failure is corrected there
> On Wed, Jun 29, 2022 at 5:00 PM Richard Biener wrote:
> >
> > On Tue, 28 Jun 2022, Kito Cheng wrote:
> >
> > > That
Committed to trunk, thanks :)
Is it OK for gcc-11 and gcc-12 branches?
On Wed, Jun 29, 2022 at 5:00 PM Richard Biener wrote:
>
> On Tue, 28 Jun 2022, Kito Cheng wrote:
>
> > That warning won't happen on ilp32 targets, seems like Andrew Pinski
> > already mention that[1] before.
> >
> > Verified
On Tue, 28 Jun 2022, Kito Cheng wrote:
> That warning won't happen on ilp32 targets, seems like Andrew Pinski
> already mention that[1] before.
>
> Verified on riscv32-unknown-elf and riscv64-unknown-elf.
>
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879#c1
OK
>
That warning won't happen on ilp32 targets, seems like Andrew Pinski
already mention that[1] before.
Verified on riscv32-unknown-elf and riscv64-unknown-elf.
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879#c1
gcc/testsuite/ChangeLog:
PR testsuite/102690
*