[flang-commits] [PATCH] D126279: [Fortran] Set QUIET = .TRUE. in STOP statements

[Diana Picus via Phabricator via flang-commits]

rovka added a comment.

I can do that <https://reviews.llvm.org/D126360>, but I don't like that solution. My understanding is that these warnings are platform-dependent, and also the 'Fortran STOP' seems to be printed by default by flang. This means pretty much anyone running the test-suite with flang will have to set this environment variable, or else face a ton of failures. Why make the test-suite harder to run? I think one of the goals of the test-suite is to be independent from both the hardware and the compiler, and all the better if it's possible to achieve that without compiler-specific hacks. In this case, setting the STOP statement to QUIET makes sense to me because its output is not strictly defined by the standard and will vary with both hardware and compiler. The test-suite is not a good place to test warnings, error messages or other fuzzy output - that should go in flang's own tests.


Repository:
  rT test-suite

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D126279/new/

https://reviews.llvm.org/D126279