News for hackers. Stuff that matters.
Re:Testing GCC by greglindahl on Monday February 13, 2017 @05:28PM (#13639407)
I never got around to actually implementing the following in the PathScale compiler, but my idea was to add logging in all the places where allocations do something, and then create lists of optimizations that I expect to have successfully fired in various functions or programs. This would be especially handy for checking that new optimizations didn't disable important things for various SPECcpu benchmarks.
Re:Testing GCC by greglindahl on Monday February 13, 2017 @09:26PM (#13640690)
Sorry, "the places where optimizations do something". Didn't notice until after the edit window was long passed. I blame autocorrect :-)