https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98605
--- Comment #4 from Jonathan Wakely ---
Doh, I missed out the actual commit hash. It was:
commit d1e85aa999ab87009fa02a5261754fbaa69206f2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98605
--- Comment #3 from Jonathan Wakely ---
(In reply to Matheus Izvekov from comment #0)
> This was caused by the following commit:
>
> ```
> commit 018813c8994b7dceab1b7d999e9c09654a22ef50
I can't identify that commit. The one in the GCC tree is:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98605
--- Comment #2 from Jonathan Wakely ---
Yes, that seems preferable, thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98605
--- Comment #1 from Matheus Izvekov ---
By the way, FYII it is also possible to suppress clang-tidy specific
diagnostics on specific lines with a "comment pragma", like so (untested):
// NOLINT(bugprone-dangling-handle)
// NOLINTNEXTLINE(bugpron
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98605
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned
