Message ID | 20230428122142.928135-1-fberat@redhat.com |
---|---|
Headers | show |
Series | Fix warn unused result | expand |
On 2023-04-28 08:21, Frédéric Bérat wrote: > Hello, > > Enabling _FORTIFY_SOURCE on Glibc itself implies that some function get the > __wur macro enabed. > This leads to build failures when -Werror is set. > > I went for multiple patches for these fixes, a big one that cover the tests, > and then separate one for the other ones, assuming they may need to get a > closer look at. > > While most of the changes look trivial, decision I made on how to fix them may > be open to debate, e.g. the additional checks may lead to failures while they > weren't earlier, some other have no impact while it may be useful to have one. > > Feedback is therefore highly appreciated. Thank you for your continued work on this; 3 down, 12 (and a bit more ;)) to go. I have pushed 3 of the patches I get R-b for. Overall for the remaining patches, there's one review note that's pertinent; the tests that you've added the x* function calls for need to use the support.h system, i.e. replace test-skeleton.c with support/test-driver.c and then replace the non-zero returns from do_test with the check.h macros. Thanks, Sid