https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729
--- Comment #4 from Vineet Gupta <vineetg at gcc dot gnu.org> --- (In reply to Jeffrey A. Law from comment #3) > Vineet, do we have this isolated enough that we know what function is most > affected and presumably the most impacted blocks? If so we can probably > start to debug scheduler dumps. I think so :-) But this is all anecdotal. The test attached was reduced from original/full ML_BSSN_RHS.ii (which granted is 2nd most spill, orig is ML_BSSN_Advect.ii which i have also reduced now). Anyhow pretty much all of file is one function and my reduction methodology was to see 1 spill with sched1 enabled and none otherwise. I hope that is representative of the pathology seen in the original/full ML_BSSN_RHS.ii > There's a flag -fsched-verbose=N that gives a lot more low level information > about the scheduler's decisions. I usually use N=99. It makes for a huge > dump, but gives extremely detailed information about the scheduler's view of > the world. I'll start diving into sched1 dumps as you suggest.
