https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93880
--- Comment #6 from Roland Illig ---
(In reply to Marek Polacek from comment #5)
> Right, but that still doesn't make it significantly easier to grep, I think.
Oh, damn, I forgot about the regular expressions.
In other contexts I have seen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93880
--- Comment #5 from Marek Polacek ---
Right, but that still doesn't make it significantly easier to grep, I think.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93880
--- Comment #4 from Andreas Schwab ---
You can use {\(reversed\)} instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93880
--- Comment #3 from Marek Polacek ---
In this particular case I'm not sure how better we could test it. Now we have:
6 bool operator==(Y, int);// #2 { dg-message "reversed" "" { target c++2a
} }
and with all the escaping in tcl I don't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93880
--- Comment #2 from Roland Illig ---
Could you perhaps make the diagnostic in the test a bit more verbose?
The word "reversed" appears 492 times in the GCC source tree, and I'm not going
through all these occurrences just to find the test for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93880
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
