https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113206
--- Comment #9 from Patrick O'Neill <patrick at rivosinc dot com> --- (In reply to JuzheZhong from comment #8) > It seems that we still didn't locate the real problem of failed SPEC you ran. > Do you have any other ideas to locale the real problem ? > > Li Pan didn't locate the problem neither. Using 4a0a8dc1b88408222b88e10278017189f6144602, the spec run failed on: zvl128b (All runtime fails): 527.cam4 (Runtime) 531.deepsjeng (Runtime) 521.wrf (Runtime) 523.xalancbmk (Runtime) zvl256b: 507.cactuBSSN (Runtime) 521.wrf (Build) 527.cam4 (Runtime) 531.deepsjeng (Runtime) 549.fotonik3d (Runtime) With that info I think the next steps are: 1. Triage the zvl256b 521.wrf build failure 2. Bisect the newly-failing testcases 3. Finish triaging the remaining testcases the fuzzer found 4. Attempt to manually reduce cam4 for zvl128b (since it seems to have the fastest build+runtime) 5. Attempt to manually reduce other fails.
