------- Comment #9 from pinskia at gcc dot gnu dot org 2007-03-20 18:57 ------- (In reply to comment #8) > Why do you say the code is undefined. The last version (comment #5) is totally > valid, but possible side effects in the function k could lead to different > results depending on the fact that the -fbounds-check is set or no.
No, the last one just shows how the code is really undefined. > And this is not a sane behaviour. Fortran is not C here sorry. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31269
