https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #31 from Hans Ecke <hansecke at gmail dot com> --- I would like to point out that what everybody here proposes - make (void) work properly with WUR - hurts no one. The other viewpoint has only given vague theoretical reasons. Let me give you something concrete: Sometimes my junior devs ask about wur-like functionality in C. My answer is "would be nice to have, right?". That is because this attribute as gcc implements it right now is useless. I'm not going to clutter my codebase with a bunch of custom macros. Please do one of the following: * my preference: make the attribute work properly, in line with C++ and clang * add a new attribute that has the behavior that 99.9% of the people actually want We've already lost 2 years. With the speed that new gcc releases make it to production systems we could use proper wur in gcc in 2023.
