https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82390
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82390
--- Comment #5 from joseph at codesourcery dot com ---
dg-options is absolutely fine in torture directories, as long as the
options specified are not among the -O options that the test should be
looping over. For example, it's fine for a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82390
Tom de Vries changed:
What|Removed |Added
Attachment #42279|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82390
--- Comment #3 from Tom de Vries ---
Created attachment 42287
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42287=edit
tentative patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82390
--- Comment #2 from Tom de Vries ---
Created attachment 42279
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42279=edit
Patch disallowing dg-options for dg-torture.exp
(In reply to Richard Biener from comment #1)
> dg-torture testcases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82390
--- Comment #1 from Richard Biener ---
dg-torture testcases should use dg-additional-options and never specify the
optimization level.
Either changing them to do that or moving out-of torture seems like a good fix.
