On Wed, Aug 28, 2024 at 9:21 AM Richard Biener <richard.guent...@gmail.com> wrote: > > On Wed, Aug 28, 2024 at 12:43 AM Edwin Lu <e...@rivosinc.com> wrote: > > > > On 8/22/2024 5:35 AM, Richard Biener wrote: > > > On Thu, Aug 22, 2024 at 1:03 AM Edwin Lu <e...@rivosinc.com> wrote: > > >> > > >> Hi, > > >> > > >> Just wanted to ping this for more guidance. > > > > > > It's difficult for me as long as I cannot investigate this with a > > > testcase. Can > > > we go ahead with the other parts so the testcase can be added and the > > > issue reproduced? > > > > > > Richard. > > > > The testcase can be found in patch 1/2 of the series > > https://inbox.sourceware.org/gcc-patches/20240530000512.2625173-2-patr...@rivosinc.com/ > > with the newly added gcc.target/riscv/rvv/autovec/no-segment.c file. > > I did find the test but the issue doesn't reproduce for me with it. > > > +cc Jeff, Palmer > > > > From what I understand reading over the threads on the previous patch > > series versions, review for patch 1/2 has been deferred until this bug > > fix has been acked so we can't move forward with the other patch yet. > > I'd say continue with review and checkin, leave the test in FAILing state > and then followup with the fix as we're stuck here otherwise.
I've now run into the corresponding case in get_group_load_store_type and we've concluded adding known_ne (remain, 0) before constant_multiple_p is the correct thing to do. I'm testing a patch that does this and sync up the vectorizable_load case. This should resolve your problem I think. Richard.
