On 11/15/2016 08:07 AM, Bruno Haible wrote:
I don't understand why you see this warning but the glibc developers
haven't noticed it yet??
I was puzzled about that too.
For what it's worth, those __THROWs were introduced to glibc in 2004 by
Ulrich Drepper, here:
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=79937577d1e3e01b3fcc618366a9d7f78feed272
with no comment explaining why. Perhaps the compilers of the time
weren't smart enough to figure this stuff out automatically for static
functions. Anyway, the __THROWs should not be needed now. I verified
that they don't affect the code generated for x86-64 on Fedora 24 (gcc
Red Hat 6.2.1-2).
