August 18, 2019 2:24 AM, "Gerald Pfeifer" gerald@pfeifer.com wrote:
(I know we're focusing on GCC, and that's what I usually do, but more often than not GCC has been adding the same warnings that clang already had. Or should we consider this a clang bug?)
When I added that attribute to Clang, we did indeed consider this a Clang bug, which I fixed. Then they did something to Clang which made it warn again.
Chip