Currently, the only way to suppress custom warnings and deprecations is
with -fno-warn-warnings-deprecations, which is a rather large hammer. I see
two ways we can improve this, and I propose that we should do both.
1. Per-binding suppression
Add -fno-warn-binding, -fno-deprecate-binding,
While I'll admit that I'm not terribly familiar with our STM
implementation, it came to mind while I was reading this article [1] on
the restartable sequences mechanism that might someday land in the Linux
kernel.
I thought you both might be interested.
Cheers,
- Ben
[1]
