https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53852
--- Comment #18 from Sebastian Pop <spop at gcc dot gnu.org> --- (In reply to Joost VandeVondele from comment #17) > since today on trunk this also triggers for options such as -floop-block, > which didn't trigger this before. Because as of yesterday both -ftree-loop-linear and -floop-block are aliases of -floop-nest-optimize, that triggers the ISL scheduler. I will have a look at the compile time and memory usage of this testcase. Thanks for the heads'up.
