[testsuite] Emit 'warning' instead of 'error' diagnostics for 'dg-optimized', 'dg...
authorThomas Schwinge <thomas@codesourcery.com>
Fri, 6 Nov 2020 08:51:16 +0000 (09:51 +0100)
committerThomas Schwinge <thomas@codesourcery.com>
Tue, 24 Nov 2020 09:28:55 +0000 (10:28 +0100)
commit54f72078fc05b865601645edafbc6b21701ea546
tree3d75c8079635c0824385a64ae03fe09540bc7126
parent24b553d0f73ffea2551a77c67859ad6fe44110a6
[testsuite] Emit 'warning' instead of 'error' diagnostics for 'dg-optimized', 'dg-missed'

The diagnostics produced by 'dg-optimized', 'dg-missed' aren't error
diagnostics (fatal, meaning: causes compilation to fail) but rather warning
diagnostics (non-fatal, doesn't cause compilation to fail).  Thus, same as
'dg-message', these should use 'saved-dg-warning' instead of 'saved-dg-error',
which then prints: "(test for *warnings*, line [...]) instead of currently:
"(test for *errors*, line [...])".

This is a small bug-fix for commit ed2d9d3720adef3a260b8a55e17e744352a901fc
"dumpfile.c: use prefixes other than 'note: ' for
MSG_{OPTIMIZED_LOCATIONS|MISSED_OPTIMIZATION}", which added 'dg-optimized',
'dg-missed'.

gcc/testsuite/
* lib/gcc-dg.exp (dg-optimized, dg-missed): Use 'saved-dg-warning'
instead of 'saved-dg-error'.
gcc/testsuite/lib/gcc-dg.exp