Fork of glibc for development https://git.zx2c4.com/glibc/atom/setjmp/bits/types?h=master 2024-01-01T18:53:40Z 2024-01-01T18:53:40Z Paul Eggert eggert@cs.ucla.edu 2024-01-01T18:12:26Z urn:sha1:dff8da6b3e89b986bb7f6b1ec18cf65d5972e307 2023-01-06T21:14:39Z Joseph Myers joseph@codesourcery.com 2023-01-06T21:08:04Z urn:sha1:6d7e8eda9b85b08f207a6dc6f187e94e4817270f 2022-01-01T19:40:24Z Paul Eggert eggert@cs.ucla.edu 2022-01-01T18:54:23Z urn:sha1:581c785bf31bc74430320c7856bbfa3875d025fe I used these shell commands: ../glibc/scripts/update-copyrights $PWD/../gnulib/build-aux/update-copyright (cd ../glibc && git commit -am"[this commit message]") and then ignored the output, which consisted lines saying "FOO: warning: copyright statement not found" for each of 7061 files FOO. I then removed trailing white space from math/tgmath.h, support/tst-support-open-dev-null-range.c, and sysdeps/x86_64/multiarch/strlen-vec.S, to work around the following obscure pre-commit check failure diagnostics from Savannah. I don't know why I run into these diagnostics whereas others evidently do not. remote: *** 912-#endif remote: *** 913: remote: *** 914- remote: *** error: lines with trailing whitespace found ... remote: *** error: sysdeps/unix/sysv/linux/statx_cp.c: trailing lines 2021-01-02T20:17:34Z Paul Eggert eggert@cs.ucla.edu 2021-01-02T19:32:25Z urn:sha1:2b778ceb4010c28d70de9b8eab20e8d88eed586b I used these shell commands: ../glibc/scripts/update-copyrights $PWD/../gnulib/build-aux/update-copyright (cd ../glibc && git commit -am"[this commit message]") and then ignored the output, which consisted lines saying "FOO: warning: copyright statement not found" for each of 6694 files FOO. I then removed trailing white space from benchtests/bench-pthread-locks.c and iconvdata/tst-iconv-big5-hkscs-to-2ucs4.c, to work around this diagnostic from Savannah: remote: *** pre-commit check failed ... remote: *** error: lines with trailing whitespace found remote: error: hook declined to update refs/heads/master 2020-10-05T16:46:46Z Joseph Myers joseph@codesourcery.com 2020-10-05T16:46:46Z urn:sha1:19302b27bdacfe87e861ff46fc0fbad60dd6602d This patch fixes part of bug 26647 (-Werror=array-parameter error building with GCC 11 because of __sigsetjmp being declared using an array parameter in one header and a pointer parameter in another). The fix is to split the struct __jmp_buf_tag definition out to a separate bits/types/ header so it can be included in pthread.h, so that pthread.h can declare __sigsetjmp with the type contents visible, so can use an array (as in setjmp.h) rather than a pointer in the declaration. Note that several other build failures with GCC 11 remain. This does not fix the jmp_buf-related -Wstringop-overflow errors (also discussed in bug 26647), or -Warray-parameter errors for other functions (bug 26686), or -Warray-bounds errors (bug 26687). Tested, with older compilers, natively for x86_64 and with build-many-glibc.py for aarch64-linux-gnu. Tested with build-many-glibcs.py with GCC mainline for aarch64-linux-gnu that this gets past the -Warray-parameter issue for __sigsetjmp (with the next build failure being the other one discussed in bug 26647).