aboutsummaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* Update in preparation for 13.3-RELEASErelease/13.3.0Colin Percival2024-03-011-1/+1
| | | | | | | | | - Bump BRANCH to RELEASE - Add the anticipated RELEASE announcement date - Set a static __FreeBSD_version Approved by: re (implicit) Sponsored by: https://www.patreon.com/cperciva
* MFC: MFV: expat 2.6.0.Xin LI2024-02-212-7/+13
| | | | | | | Approved by: re (cperciva) (cherry picked from commit 4543ef516683042d46f3bd3bb8a4f3f746e00499) (cherry picked from commit 60cfaec917dad12ceab7450a518616668d9f1ed0)
* login_cap.h: Remove LOGIN_DEFPRIOlivier Certner2024-02-012-2/+1
| | | | | | | | | | | | | | | | | | | | | | | This is an implementation detail which is likely to become irrelevant in the future, as we move to not resetting the priority if the corresponding capability is not present in the configuration file ('/etc/login.conf'). GitHub's code search and Google show no use of this public constant, and it doesn't exist in OpenBSD and NetBSD. So, remove this definition and its sole use in-tree. PR: 276570 (exp-run) Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43609 (cherry picked from commit c7e645269f1c7e9872a7ccf6b72f045c55a66793) Approved by: markj (mentor)
* login_cap.h: Remove LOGIN_DEFUMASKOlivier Certner2024-02-011-1/+0
| | | | | | | | | | | | | | | | | | | | This public constant has not been used in-tree since 1997 (this was noticed while working on previous commit "setusercontext(): umask: Set it only once (in the common case)"). Since it was an implementation detail and GitHub's code search and Google show no use of this symbol today, simply remove it. PR: 276570 (exp-run) Reviewed by: emaste, kib (earlier version, then part of D40344) Approved by: emaste (mentor) MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43608 (cherry picked from commit e3a396eb2a029e5dc9161469735aa3f7f16845d1) Approved by: markj (mentor)
* setusercontext(): Set priority from '~/.login_conf' as wellOlivier Certner2024-02-011-0/+2
| | | | | | | | | | | | | | | | | | | | Setting the process priority is done only when the current process' effective UID corresponds to that for which context is to be set. Consequently, setting priority is done with appropriate credentials and will fail if the target user tries to raise it unduly via his '~/.login_conf'. PR: 271751 Reviewed by: kib, Andrew Gierth <andrew_tao173.riddles.org.uk> Approved by: emaste (mentor) MFC after: 3 days Relnotes: yes Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40352 (cherry picked from commit f2a0277d3e51a6a839151eef17f466d0db2b7300) Approved by: markj (mentor)
* login.conf(5): Document priority's special value 'inherit'Olivier Certner2024-02-011-0/+3
| | | | | | | | | | | | Reviewed by: emaste, yuripv (older version) Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40691 (cherry picked from commit 33d4ce5496efe96bbaa7663e298876395b1db62c) Approved by: markj (mentor)
* setclasspriority(): New possible value 'inherit'Olivier Certner2024-02-011-1/+7
| | | | | | | | | | | | | | | | | | It indicates to the login.conf machinery (setusercontext() / setclasscontext()) to leave priority alone, effectively inheriting it from the parent process. PR: 271749 Reviewed by: emaste, yuripv Approved by: emaste (mentor) MFC after: 3 days Relnotes: yes Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40690 (cherry picked from commit d162d7e2ad327ceada4102c5d6779f9ecd809502) Approved by: markj (mentor)
* setusercontext(): Move priority setting in new setclasspriority()Olivier Certner2024-02-011-45/+52
| | | | | | | | | | | | | | | | | In preparation for setting priorities from '~/.login_conf' and to ease reading of setusercontext(). No functional change. Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40350 (cherry picked from commit 7b94ec550ef6e7b75d608e125e9b78478197d4e7) Approved by: markj (mentor)
* login.conf(5): Document priority's default and possible valuesOlivier Certner2024-02-011-1/+15
| | | | | | | | | | | | | | | | | | Priority is reset to 0 if not explicitly specified. While here, be more explicit about what "Initial priority (nice) level" means and document that it is possible to set real-time or idle class' priorities with this capability. Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40689 (cherry picked from commit aa96945e71b0f724e6ce673194d23f58d2d637d3) Approved by: markj (mentor)
* setusercontext(): Better error messages when priority is not set correctlyOlivier Certner2024-02-011-17/+34
| | | | | | | | | | | | | | | | | | | | Polish the syslog messages to contain readily useful information. Behavior of capability 'priority' is inconsistent with what is done for all other contexts: 'umask', 'cpumask', resource limits, etc., where an absence of capability means to inherit the value. It is currently preserved for compatibility, but is subject to change on a future major release. Reviewed by: emaste, kib (older version) Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40349 (cherry picked from commit d988621b0c25209866ed5a98b1a8b20269935761) Approved by: markj (mentor)
* login.conf(5): Default values: Rename column, elaborate on absence of suchOlivier Certner2024-02-011-4/+10
| | | | | | | | | | | | | | | | | | | Column "Notes" in fact only contains default values for capabilities, so make this clear by renaming it to "Default". Add a small introductory text mentioning it, and what an absence of default value means (inheritance). PR: 271748 Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40347 (cherry picked from commit 92b2c4358f57ef84f161efd8370ba4832bd9261a) Approved by: markj (mentor)
* setlogincontext(): Comply to style(9)Olivier Certner2024-02-011-17/+22
| | | | | | | | | | | | | | | Remove indentation by inverting the big 'if (lc)' and using 'return'. Use explicit binary operators to produce booleans. Reviewed by: emaste, kib, dchagin Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40346 (cherry picked from commit 771d5c93ab5a3fb1701d9706df2ce87d6a9da6f3) Approved by: markj (mentor)
* login.conf(5): Document umask's special value 'inherit'Olivier Certner2024-02-011-0/+3
| | | | | | | | | | | | Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40688 (cherry picked from commit ea9bd448102b938ccb8d4b484684a6ba2d934931) Approved by: markj (mentor)
* setclassumask(): Accept 'inherit' as a valueOlivier Certner2024-02-011-1/+12
| | | | | | | | | | | | | | | 'inherit' explicitly indicates that the umask should not be changed. Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Relnotes: yes Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40687 (cherry picked from commit c328e6c6ccaa4cdf921c16d68a2f2c5992dd3b72) Approved by: markj (mentor)
* setusercontext(): Set umask in a separate function, setclassumask()Olivier Certner2024-02-011-26/+33
| | | | | | | | | | | | Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40686 (cherry picked from commit 0dd1705f584947625892988afe59e4cedb5cdd09) Approved by: markj (mentor)
* login_cap(3): Document login_getcapenum()Olivier Certner2024-02-011-0/+28
| | | | | | | | | | | | Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40685 (cherry picked from commit 97256feb7a65cccac51a03846c5308894a2cb445) Approved by: markj (mentor)
* New login_getcapenum(): Allows to read named enum valuesOlivier Certner2024-02-012-0/+48
| | | | | | | | | | | | Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40684 (cherry picked from commit 90e914cd5ac1c8ecbf1ea88e9a65e7fa866c17a9) Approved by: markj (mentor)
* login.conf(5): umask has no default valueOlivier Certner2024-02-011-1/+1
| | | | | | | | | | | | | | | | The umask is simply left unchanged if no explicit value is specified in the login class capabilities database. PR: 271747 Reviewed by: emaste Approved by: emaste (mentor) MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40345 (cherry picked from commit 0d1fe948d97d2d6e3708349b74cf438f9604a8d1) Approved by: markj (mentor)
* setusercontext(): umask: Set it only once (in the common case)Olivier Certner2024-02-011-14/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Simplify the code and make it more coherent (umask was the only context setting not modified by setlogincontext() directly). Preserve the current behavior of not changing the umask if none is specified in the login class capabilities database, but without the superfluous umask() dance. (The only exception to this is that a special value no user is likely to input in the database now stands for no specification.) If some user has a 'umask' override in its '~/.login_conf', the umask will still be set twice as before (as is the case for all other context settings overriden in '~/.login_conf'). Log a warning in case of an invalid umask specification. This change makes it apparent that the value of LOGIN_DEFUMASK doesn't matter. It will be removed in a subsequent commit. PR: 271747 Reviewed by: emaste, kib (earlier version) Approved by: emaste MFC after: 3 days Sponsored by: Kumacom SAS Differential Revision: https://reviews.freebsd.org/D40344 (cherry picked from commit e99c28e93bd4d04ff877459734e9ce06ad2335a7) Approved by: markj (mentor)
* open(2): describe *at behavior for dirfd opened without O_SEARCHKonstantin Belousov2024-02-011-14/+24
| | | | (cherry picked from commit a570fe4d0dd979ce099374259ffc45d56ae4e471)
* inet(3): clarify syntax accepted by inet_ptonMike Karels2024-01-301-9/+15
| | | | | | | | | | | | | | | The section INTERNET ADDRESSES describes the acceptance of dotted values with varying number of parts in multiple bases. This applies to inet_aton and inet_addr, but not to inet_pton. Clarify this section by listing the functions to which this applies. Move the description of what inet_pton accepts into this section from STANDARDS, where it is easily missed. Rename the section to clarify that it applies only to IPv4. (inet_pton also works with IPv6.) Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D43537 (cherry picked from commit 9231c42127bf8e47588169ecc395f57cae0e15fb)
* Add libllvm and liblldb source files to enable WITH_ASAN buildDimitry Andric2024-01-302-0/+7
| | | | | | | | | | | | This is another part of fixing the WITH_ASAN build. Some additional source files had to be added to libllvm and liblldb, since the ASan instrumentation causes symbols in those files to be referenced. Reported by: markj PR: 276597 MFC after: 3 days (cherry picked from commit 5c38ea60a04199dae2c6e5db82461e7275c7def6)
* msun: remove fabs from Symbol.map, and adjust commentDimitry Andric2024-01-302-2/+2
| | | | | | | | | | | | | | | | | We have s_fabs.c, but fabs(3) is already provided by libc due to historical reasons, so it is not compiled into libm. When the linker does not use --undefined-version, this leads to a complaint about the symbol being nonexistent, so remove it from Symbol.map. While here, adjust the comment about some functions being supplied by libc: while it is true that all these are indeed in libc, libm still includes its own versions of frexp(3), isnan(3), isnanf(3), and isnanl(3). Reported by: Steve Kargl <sgk@troutmask.apl.washington.edu> MFC after: 3 days (cherry picked from commit d04e03c19a8d7660ea36f62720eef9bc96b69889)
* pthread_attr_get_np(): Use malloc(), report ENOMEM, don't tamper on errorOlivier Certner2024-01-262-20/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Similarly as in the previous commit, using calloc() instead of malloc() is useless here in the regular case since the subsequent call to cpuset_getaffinify() is going to completely fill the allocated memory. However, there is an additional complication. This function tries to allocate memory to hold the cpuset if it previously wasn't, and does so before the thread lock is acquired, which can fail on a bad thread ID. In this case, it is necessary to deallocate the memory allocated in this function so that the attributes object appears unmodified to the caller when an error is returned. Without this, a subsequent call to pthread_attr_getaffinity_np() would expose uninitialized memory (not a security problem per se, since it comes from the same process) instead of returning a full mask as it would before the failing call to pthread_attr_get_np(). So the caller would be able to notice a change in the state of the attributes object even if pthread_attr_get_np() reported failure, which would be quite surprising. A similar problem that could occur on failure of cpuset_setaffinity() has been fixed. Finally, we shall always report memory allocation failure. This already goes for pthread_attr_init(), so, if for nothing else, just be consistent. Reviewed by: emaste, kib Approved by: emaste (mentor) MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43329 (cherry picked from commit aadb4a1b3fd185d547087f6eafca6ce0b4df3291) Approved by: markj (mentor)
* libhtr: pthread_attr_setaffinity_np(): Replace calloc() with malloc()Olivier Certner2024-01-261-1/+1
| | | | | | | | | | | | | | | Using calloc() instead of malloc() is useless here since the allocated memory is to be wholly crushed by the memcpy() call that follows. Suggested by: kib Reviewed by: emaste, kib Approved by: emaste (mentor) MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D43328 (cherry picked from commit 15bb0300eeca233827a6a13cd2ed883e0034979d) Approved by: markj (mentor)
* libthr: thr_attr.c: More style and clarity fixesOlivier Certner2024-01-261-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | The change of argument for sizeof() (from a type to an object) is to be consistent with the change done for the malloc() code just above in the preceding commit touching this file. Consider bit flags as integers and test whether they are set with an explicit comparison with 0. Use an explicit flag value (PTHREAD_SCOPE_SYSTEM) in place of a variable that has this value at point of substitution. All other changes are straightforward. Suggested by: kib Reviewed by: kib Approved by: emaste (mentor) MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D43327 (cherry picked from commit 4d312aa051414ad77d3515f258230d01ad11d6dc) Approved by: markj (mentor)
* _umtx_op.2: Fix a typo in the manual pageGordon Bergling2024-01-231-1/+1
| | | | | | - s/interpeted/interpreted/ (cherry picked from commit b2ec175fcaac90fc6a1caf066656eaa092f32611)
* sigfastblock.2: Fix a typo in the manual pageGordon Bergling2024-01-231-1/+1
| | | | | | - s/successfull/successful/ (cherry picked from commit a70008e95b907336bddbcc2aa9d567df6e3a41b6)
* pkru.3: Fix a typo in the manual pageGordon Bergling2024-01-231-1/+1
| | | | | | - s/successfull/successful/ (cherry picked from commit 8593b5b2addf91987f81ebac0d8b2e51207e4793)
* Remove _POSIX_PRIORITIZED_IO references from man pagesAlan Somers2024-01-193-28/+2
| | | | | | | | | | | | | We don't support it, so there's no need to tell readers what would happen if we did. Also, don't remind the user that a certain field is ignored by aio_read. Mentioning every ignored field would make the man pages too verbose. Sponsored by: Axcient Reviewed by: Pau Amma <pauamma@gundo.com> Differential Revision: https://reviews.freebsd.org/D42622 (cherry picked from commit 18e2c4175f78f1aaa648dd7fb7530220aed23671)
* cap_net.3: remove a copypastaAlan Somers2024-01-191-6/+3
| | | | | | | | | | | | | This line appears to have been copied from cap_sysctl.3. While I'm here, reorder and reword the description of cap_net_limit a bit. [skip ci] Sponsored by: Axcient Reviewed by: oshogbo Differential Revision: https://reviews.freebsd.org/D42919 (cherry picked from commit 6b96125afdf245ae61dd82b59891ad0d6aab0066)
* sigaction.2: clarify that fork isn't async-signal-safe, but _Fork isAlan Somers2024-01-191-2/+2
| | | | | | | | | | [skip ci] Sponsored by: Axcient Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D42865 (cherry picked from commit c2ed7a63604fc86244adee2966e19f8aba2a07cb)
* libthr: thr_attr.c: EINVAL, not ENOTSUP, on invalid argumentsOlivier Certner2024-01-181-13/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On first read, POSIX may seem ambiguous about the return code for some scheduling-related pthread functions on invalid arguments. But a more thorough reading and a bit of standards archeology strongly suggests that this case should be handled by EINVAL and that ENOTSUP is reserved for implementations providing only part of the functionality required by the POSIX option POSIX_PRIORITY_SCHEDULING (e.g., if an implementation doesn't support SCHED_FIFO, it should return ENOTSUP on a call to, e.g., sched_setscheduler() with 'policy' SCHED_FIFO). This reading is supported by the second sentence of the very definition of ENOTSUP, as worded in CAE/XSI Issue 5 and POSIX Issue 6: "The implementation does not support this feature of the Realtime Feature Group.", and the fact that an additional ENOTSUP case was added to pthread_setschedparam() in Issue 6, which introduces SCHED_SPORADIC, saying that pthread_setschedparam() may return it when attempting to dynamically switch to SCHED_SPORADIC on systems that doesn't support that. glibc, illumos and NetBSD also support that reading by always returning EINVAL, and OpenBSD as well, since it always returns EINVAL but the corresponding code has a comment suggesting returning ENOTSUP for SCHED_FIFO and SCHED_RR, which it effectively doesn't support. Additionally, always returning EINVAL fixes inconsistencies where EINVAL would be returned on some out-of-range values and ENOTSUP on others. Reviewed by: markj Approved by: markj (mentor) MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43006 (cherry picked from commit 0eccb45979a8ee3129e11b638ebc4cfa00942b80) Approved by: markj (mentor)
* libthr: thr_attr.c: Clarity, whitespace and styleOlivier Certner2024-01-181-273/+188
| | | | | | | | | | | | | | Also, remove most comments, which don't add value. Reviewed by: emaste Approved by: markj (mentor) MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43005 (cherry picked from commit bd61c1e89dc4a40ba696de1785d423978e1c2147) Approved by: markj (mentor)
* resolv: Add a required include to resolv.hJan Beich2024-01-151-4/+1
| | | | | | | | | | Add a required include to resolv.h for sockaddr_in. This should reduce patching required when porting code written with Linux or NetBSD in mind. PR: 182466 MFC after: 1 week (cherry picked from commit 58cf91d3b72a01777bacf72d66a648a744ae3143)
* setfib.2: Consistently capitalize "FIB"Mark Johnston2024-01-111-4/+4
| | | | | | | MFC after: 1 week Sponsored by: Klara, Inc. (cherry picked from commit ee7d5ba1b55441476643983d3f70df5ee9ea97c4)
* copy_file_range.2: Clarify that only regular files workRick Macklem2024-01-111-5/+13
| | | | | | | | | | | | | | | | | | | PR#273962 reported that copy_file_range(2) did not work on shared memory objects and returned EINVAL. Although the reporter felt this was incorrect, it is what the Linux copy_file_range(2) syscall does. Since there was no collective agreement that the FreeBSD semantics should be changed to no longer be Linux compatible, copy_file_range(2) still works on regular files only. This man page update clarifies that. If, someday, copy_file_range(2) is changed to support non-regular files, then the man page will need to be updated to reflect that. PR: 273962 (cherry picked from commit 84b4342c0d7ac8a3187309a978d41e6765154cc1)
* Add missing /usr/include/c++/v1/__mdspan/mdspan.h headerDimitry Andric2024-01-071-0/+1
| | | | | | | | | I missed this header while updating the Makefile for libc++ 17. PR: 273753 MFC after: 1 month (cherry picked from commit 87eea35e3f8bc559a5142d613826100b758c08fe)
* Add missing sources to libclang_rt Makefiles, clean up unneeded onesDimitry Andric2024-01-0711-13/+10
| | | | | | | | | | | | | | | | | | During the llvm-17 merge, a few new source files were not added to the libclang_rt Makefiles, in particular sanitizer_thread_arg_retval.cpp which is now required for AddressSanitizer and MemorySanitizer. Also, MemorySanitizer now requires msan_dl.cpp. While here, clean out a number of source files that compile into nothing (because they only contain non-FreeBSD parts). Also, remove a duplicated instance of tsan_new_delete.cpp from libclang_rt.tsan, since it is only supposed to live in libclang_rt.tsan_cxx. PR: 275854 Reported by: jbeich MFC after: 1 month (cherry picked from commit 0c3af23961e170538f375c392b043903c1397780)
* Merge llvm-project release/17.x llvmorg-17.0.6-0-g6009708b4367Dimitry Andric2024-01-077-15/+15
| | | | | | | | | | This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp to llvmorg-17.0.6-0-g6009708b4367. PR: 273753 MFC after: 1 month (cherry picked from commit 5c16e71d30c388dd43b217de10a3ccb4b0219d0d)
* Merge llvm-project release/17.x llvmorg-17.0.5-0-g98bfdac5ce82Dimitry Andric2024-01-077-15/+15
| | | | | | | | | | This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp to llvmorg-17.0.5-0-g98bfdac5ce82. PR: 273753 MFC after: 1 month (cherry picked from commit b121cb0095c8c1a060f66a8c4b118a54ebaa2551)
* Merge llvm-project release/17.x llvmorg-17.0.3-0-g888437e1b600Dimitry Andric2024-01-077-15/+15
| | | | | | | | | | This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp to llvmorg-17.0.3-0-g888437e1b600. PR: 273753 MFC after: 1 month (cherry picked from commit bdb86d1a853a919764f65fdedcea76d76e4d619b)
* Merge llvm-project release/17.x llvmorg-17.0.2-0-gb2417f51dbbdDimitry Andric2024-01-073-5/+5
| | | | | | | | | | This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp to llvmorg-17.0.2-0-gb2417f51dbbd. PR: 273753 MFC after: 1 month (cherry picked from commit 3bd749dbd90cc3b95719b65393df5ca8a0fe919d)
* Merge llvm-project release/17.x llvmorg-17.0.1-25-g098e653a5bedDimitry Andric2024-01-078-22/+30
| | | | | | | | | | This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp to llvmorg-17.0.1-25-g098e653a5bed. PR: 273753 MFC after: 1 month (cherry picked from commit 4542f901cb0c5dd66ab5b541f2fbc659fd46f893)
* Merge llvm-project release/17.x llvmorg-17.0.0-rc4-10-g0176e8729ea4Dimitry Andric2024-01-078-50/+36
| | | | | | | | | | This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp to llvmorg-17.0.0-rc4-10-g0176e8729ea4. PR: 273753 MFC after: 1 month (cherry picked from commit 8a4dda33d67586ca2624f2a38417baa03a533a7f)
* Merge llvm-project main llvmorg-17-init-19304-gd0b54bb50e51Dimitry Andric2024-01-0740-6163/+10721
| | | | | | | | | | | This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb and openmp to llvm-project main llvmorg-17-init-19304-gd0b54bb50e51, the last commit before the upstream release/17.x branch was created. PR: 273753 MFC after: 1 month (cherry picked from commit 06c3fb2749bda94cb5201f81ffdb8fa6c3161b2e)
* arm64 lib32: change clang to allow -m32 on arm64Mike Karels2024-01-071-1/+1
| | | | | | | | | | | | | | | | The FreeBSD driver support for clang tested explicitly for 32-bit Intel, MIPS, or PowerPC targets where /usr/lib32/libcrt1.o was present to decide whether -m32 should use /usr/lib32. At jrtc27's suggestion, simply test for a 32-bit platform rather than adding arm to the list. Upstreamed as https://github.com/llvm/llvm-project/commit/3450272fc281979388bb845a9fffb59b42cc2e7e Bump the freebsd version to force a bootstrap build. This is one step in adding support for -m32 on arm64. Reviewed by: jrtc27, brooks, dim Differential Revision: https://reviews.freebsd.org/D40943 (cherry picked from commit f1d5183124d3e18d410ded61e45adb9a23b23c83)
* make cross build from arm64 work..John-Mark Gurney2024-01-071-0/+3
| | | | | | | | Reviewed by: dim, imp, emaste MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D38762 (cherry picked from commit eb81dd8404e55c8e048acfb1cd4f4c3c021afaf4)
* build target triple variable from sys/conf/newvers.shAlfredo Dal'Ava Junior2024-01-071-3/+6
| | | | | | | | | | | | | Retrieve FreeBSD revision number directly from sys/conf/newvers.sh when building the compiler target triple value, avoiding manual intervention on other files every new release. Reviewed by: imp MFC after: 2 months Sponsored by: Instituto de Pesquisas Eldorado (eldorado.org.br) Differential Revision: https://reviews.freebsd.org/D34429 (cherry picked from commit f9ee4156741a205c93ae947595b5c48717107d9e)
* libifconfig: Fix bridge status member listMichael Gmelin2024-01-051-1/+1
| | | | | | | | | | | | | | | | | When this functionality was moved to libifconfig in 3dfbda3401abea84da9, the end of list calculation was modified for unknown reasons, practically limiting the number of bridge member returned to (about) 102. This patch changes the calculation back to what it was originally and adds a unit test to verify it works as expected. Reported by: Patrick M. Hausen (via ML) Reviewed by: kp Approved by: kp MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D43135 (cherry picked from commit 3d36053ca6d6a17d408c8f92c504e6135dc9d8df)
generated by cgit v1.3 (git 2.53.0) at 2026-05-29 20:39:47 +0000