https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115372
--- Comment #3 from Patrick O'Neill <patrick at rivosinc dot com> --- (In reply to Richard Biener from comment #2) > I don't remember seeing FAIL: gcc.dg/vect/pr97428.c in the precommit CI, this > one should get one SLP instance and seeing zero means it now fails to SLP on > RISC-V. With a cross and rv64gcv I don't see this failure (on top of trunk). > Ah, for me it's XFAILed because of ! vect_hw_misalign - do you use additional > flags? But even adding -mno-strict-align doesn't help. > > Oh, the dejagnu harness uses check_effective_target_riscv_v_misalign_ok > which _runs_ a testcase ... which of course fails for my simple cc1 cross > (w/o binutils and w/o qemu set up). Is the precommit CI any better here? I was reviewing older bugzillas - sorry, not sure how this reply slipped through my email. The failure appears on the corresponding pre-commit: https://github.com/ewlu/gcc-precommit-ci/issues/1580#issuecomment-2127348219 Since it doesn't show up on the main cohort of common fails (7/8 targets) it got split out into sections for the targets that manifest that failure under: # Architecture Specific New Failures Splitting the results like this might be a case of bad UX on the CI's part - the goal was to prevent making too large of a comment and having to trim it. I'll think some more about if there's a better way to present/format this.
