https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113087
--- Comment #42 from Patrick O'Neill <patrick at rivosinc dot com> --- (In reply to JuzheZhong from comment #41) > Hi, Patrick. > > Could you trigger test again base on latest trunk GCC? > > We have recent memory-hog fix patch: > https://gcc.gnu.org/git/?p=gcc.git;a=commit; > h=3132d2d36b4705bb762e61b1c8ca4da7c78a8321 > > I want to make sure it doesn't cause a regression on SPEC. > > I have tested it with full coverage GCC testsuite, no regression. > > But I want to know about SPEC 2017 I kicked off a run roughly 10 hours ago with your memory-hog fix patch applied to a1b2953924c451ce90a3fdce6841b63bf05f335f. I'll post the results here when the runs complete. Thanks!
