https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53957
--- Comment #22 from Anthony <prop_design at protonmail dot com> --- (In reply to Thomas Koenig from comment #21) > Another question: Is there anything left to be done with the > vectorizer, or could we remove that dependency? thanks for looking into this again for me. i'm surprised it worked the same on Linux, but knowing that, at least helps debug this issue some more. I'm not sure about the vectorizer question, maybe that question was intended for someone else. the runtimes seem good as is though. i doubt the auto-parallelization will add much speed. but it's an interesting feature that i've always hoped would work. i've never got it to work though. the only code that did actually implement something was Intel Fortran. it implemented one trivial loop, but it slowed the code down instead of speeding it up. the output from gfortran shows more loops it wants to run in parallel. they aren't important ones. but something would be better than nothing. if it slowed the code down, i would just not use it. there is something different in gfortran where it mentions a lot of 16bit vectorization. i don't recall that from the past. but whatever it's doing, seems fine from a speed perspective. some compliments to the developers. the code compiles very fast compared to other compilers. i'm really glad it doesn't rely on Microsoft Visual Studio. that's a huge time consuming install. I was very happy I could finally uninstall it. also, gfortran handles all my stop statements properly. PGI Community Edition was adding in a bunch of non-sense output anytime a stop command was issued. So it's nice to have the code work as intended again.
