FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.3.0 2018-04-18T19:18:14Z 2018-04-18T19:18:14Z Cy Schubert cy@FreeBSD.org 2018-04-18T19:18:14Z urn:sha1:041ca5003745c04f57b13bf4a41cac8c72589515 Add new gets_s(3) stdio function. This implements the gets_s(3) function as documented at http://en.cppreference.com/w/c/io/gets. It facilitates the optional removal of gets(3). Reviewed by: ed Relnotes: yes Differential Revision: https://reviews.freebsd.org/D12785 2018-03-29T02:50:57Z Eitan Adler eadler@FreeBSD.org 2018-03-29T02:50:57Z urn:sha1:4ab2e064d7950be84256d671a7ae93f87cc6aa36 This was intended to be a non-functional change. It wasn't. The commit message was thus wrong. In addition it broke arm, and merged crypto related code. Revert with prejudice. This revert skips files touched in r316370 since that commit was since MFCed. This revert also skips files that require $FreeBSD$ property changes. Thank you to those who helped me get out of this mess including but not limited to gonzo, kevans, rgrimes. Requested by: gjb (re) 2018-03-14T03:19:51Z Eitan Adler eadler@FreeBSD.org 2018-03-14T03:19:51Z urn:sha1:be5d0b9566b13fdf8cabebb63334cbec12bfc409 These changes are incomplete but are making it difficult to determine what other changes can/should be merged. No objections from: pfg 2017-06-01T14:49:53Z Eric van Gyzen vangyzen@FreeBSD.org 2017-06-01T14:49:53Z urn:sha1:bfccc82170863098c1277c536e8e3d42a9a229d8 libthr: fix warnings at WARNS=6 Fix warnings about the following when WARNS=6 (which I will commit soon): - casting away const - no previous 'extern' declaration for non-static variable - others as explained by #pragmas and comments - unused parameters libthr: disable thread-safety warnings These warnings don't make sense for code that implements the locking primitives. libthr: change CHECK_AND_INIT_RWLOCK to an inline function This was prompted by a compiler warning about 'ret' shadowing a local variable in the callers of the macro. libthr: Use CLI flags instead of pragmas to disable warnings People tweaking the build system or compilers tend to look into the Makefile and not into the source. Having some warning controls in the Makefile and some in the source code is surprising. Pragmas have the advantage that they leave the warnings enabled for more code, but that advantage isn't very relevant in these cases. libthr: fix warnings from GCC when WARNS=6 Fix warnings about: - redundant declarations - a local variable shadowing a global function (dlinfo) - an old-style function definition (with an empty parameter list) - a variable that is possibly used uninitialized libthr: prevent setcontext() from masking SIGTHR __thr_setcontext() mistakenly tested for the presence of SIGCANCEL in its local ucontext_t instead of the parameter. Therefore, if a thread calls setcontext() with a context whose signal mask contains SIGTHR (a.k.a. SIGCANCEL), that signal will be blocked, preventing the thread from being cancelled or suspended. Sponsored by: Dell EMC 2017-03-14T20:14:57Z Pedro F. Giffuni pfg@FreeBSD.org 2017-03-14T20:14:57Z urn:sha1:0685b1047a24502ae7061889c18f282bce657dca Make use of clang nullability attributes in C headers. Replace uses of the GCC __nonnull__ attribute with the clang nullability qualifiers. These are starting to get use in clang's static analyzer. Replacement should be transparent for developers using clang. GCC ports from older FreeBSD versions may need updating if the compiler was built before r312860 (Jan-27-2017). Hinted by: Apple's Libc-1158.20.4, Bionic libc Relnotes: yes 2016-10-08T14:07:34Z Eric van Gyzen vangyzen@FreeBSD.org 2016-10-08T14:07:34Z urn:sha1:3610dd844894137b7232138a137e0fe43af91e65 Add the __printflike attribute to the declarations of dprintf(3) and vdprintf(3). Sponsored by: Dell EMC 2016-05-12T22:13:12Z Conrad Meyer cem@FreeBSD.org 2016-05-12T22:13:12Z urn:sha1:9183be81a7999622ed298f0fbc19bdf3de7d091b I'm still not sure why only Pypy runs into the error with the function typedefs. Fix it anyway. Use __ssize_t instead of ssize_t for the types; it's possible for the size_t type to not be visible if at the wrong POSIX_VISIBLE level. A final (crossing my fingers) follow-up to r299456. Sponsored by: EMC / Isilon Storage Division 2016-05-12T21:18:17Z Conrad Meyer cem@FreeBSD.org 2016-05-12T21:18:17Z urn:sha1:6710d21d9f7fce14cb77dc30c16f32e8705bf201 Despite the private namespace, several broken ports depend on the __off64_t name for the type. Export it exactly the same way off_t and __off_t are exported. A follow-up to r299456. Suggested by: php56 Sponsored by: EMC / Isilon Storage Division 2016-05-11T14:38:27Z Conrad Meyer cem@FreeBSD.org 2016-05-11T14:38:27Z urn:sha1:877a840c080f5064aa0c9b1d326f306059f0a186 Reviewed by: jhb, oshogbo Sponsored by: EMC / Isilon Storage Division Differential Revision: https://reviews.freebsd.org/D6282 2015-10-28T14:40:02Z Andrey A. Chernov ache@FreeBSD.org 2015-10-28T14:40:02Z urn:sha1:8b63538d89ef0b1b1d38532c6ff15b4f0676d7d5 Rewrite O_APPEND flag checking using new __S2OAP flag. MFC after: 3 weeks