I wonder if there is a way to disable the warning or increase the threshold just for this function. I don't think attribute optimize would work, but perhaps some pragma?Here's what I would have guessed, the pragma approach seems a little broken. https://godbolt.org/z/vY7fGYv7f Maybe I'm holding it wrong?
Thanks. Looks like the warning setting is not propagated to the point where the warning is generated in the backend. Could file a gcc bug on that, but yes the solution won't work for now.
-Andi
