[ORC] Export perf JIT loader wrapper symbols with LLVM_ALWAYS_EXPORT
PerfSupportPlugin resolves llvm_orc_registerJITLoaderPerf{Start,End,Impl} dynamically from process symbols, which fails when static executables are built with -fvisibility=hidden (e.g. CFI bootstrap builds).
Assisted-by: Gemini
[cfi] Ignore cfi-icall on LLVMContext::yield and JIT calls
LLVMContextSetYieldCallback casts a C callback with a mismatched pointer type, and ExecutionEngine / JIT tools invoke runtime-generated JIT code outside the link-time CFI jump table.
Assisted-by: Gemini
tests/sys/netinet/tcp_socket: fix build with ATF 0.22+
Confirm that creating clients/sockets was successful by testing the
result separate from the assignment and test that the return value is
not -1 instead of testing that the value returned is non-zero.
This fixes the build with [ATF 0.22+][1].
MFC after: 2 weeks
Reported by: clang (-Wparenthesis)
Reviewed by: tuexen, cc
Differential Revision: https://reviews.freebsd.org/D59284
[1]: https://github.com/freebsd/atf/pull/72
Conflicts:
tests/sys/netinet/tcp_implied_connect.c
(cherry picked from commit 4aea6ea2eb400737837ff8d22c25688f88c7966c)
[VPlan] Use mayWriteToMemory to pick early-exit style (NFC). (#237101)
Replace the store pattern match in handleUncountableEarlyExits with a
check for any recipe that may write to memory, now that call
VPInstructions model call-site attributes. Pseudo-probes are skipped,
consistent with legality, which ignores them.
This removes the blanket store check and accounts for other recipes with
side-effects via an assert.
PR: https://github.com/llvm/llvm-project/pull/237101
contrib/atf: upgrade to 0.26
This new version gets contrib/atf in line with the published version of
the package up on [GitHub][github].
Please note that this release is a major update: it contains several
bugfixes and feature enhancements. Most were already present in the
FreeBSD src repo, but there were a large number of changes made in
addition to what was already present.
MFC after: 1 month
Merge commit '9c78088348bcf1059d82a62bb57a0746309d4312'
Conflicts:
ObsoleteFiles.inc
contrib/atf/.cirrus.yml
contrib/atf/Makefile.am
contrib/atf/Makefile.in
[53 lines not shown]
ZTS: import_rewind_metadata_damaged: allow the checkpointed state
The test noted the last synced txg after "zpool checkpoint" and required
the rewind past the damaged txg to report exactly that txg. That txg is
not protected by the checkpoint: the checkpoint is created by a sync
task that records the previous synced uberblock, so the txg the test
noted is the one that creates the checkpoint (or a later one), and the
blocks it allocates (its MOS root among them) are freed by the overwrite
and can be reused by the txgs the export syncs. When that happens the
txg fails to load ("unable to open rootbp in dsl_pool_init", or "unable
to retrieve MOS config") and the rewind correctly goes on to the
checkpointed state, an older txg, and the test fails with "The txg N was
not reported as the rewind target". This is the same misconception as
#19077 in import_relax_metadata_damaged.
Read the txg of the checkpointed state with zdb (a new
get_checkpointed_txg helper) and accept any rewind target from that
state up to the txg noted before the overwrite. A rewind to the
checkpointed state itself leaves no checkpoint behind, so check the
[4 lines not shown]
[LoopUnrollAndJam] Jamming Outside Loop for stencil
Previously, we only tried to jam the loop if there was any
loop-invariant memory usage. This makes our UnrollAndJam quite
limited. GCC (gimple-loop-jam.cc) also handles stencils. What they do
is, for each MemRef pair, check the distance vector and allow jamming
if the vector is lexicographically positive.
Our safety checker (checkDependency) already allows these cases. To
match GCC's behavior, we try to calculate the actual step for each
memory usage using SCEV and find the maximum ReuseCount. Note that our
safety checker has already guaranteed that this is a forward edge, so
we don't need any additional safety checks here.
With this change running over llvm-test-suites. We observe a speedup
over my Ryzen 9 9955HX in some cases (Shootout-C++-ary3 (-34.6%),
oopack_v1p8 (-6.0%)).
Assisted by: Claude # Testcases
L2ARC: Do not write encrypted buffers whose MAC differs
When compressed ARC is disabled, l2arc_apply_transforms() compresses
an encrypted buffer again and encrypts the result with the block's
salt and IV. If the compressor's output differs from the bytes on
disk, for example for a block written before an update of the
compressor, the MAC differs from the one saved in the header too. A
debug build then panics on the ASSERT0() that compares them, and a
release build writes a copy that fails its checksum when read back.
Skip the write instead, as is already done when the recompressed
buffer does not fit in its original size: the caller clears
ARC_FLAG_L2CACHE, so the buffer is not tried again until it is
accessed again, and no L2ARC accounting has been done for it yet.
Keep asserting for a buffer that was not recompressed, whose MAC can
only differ through a bug elsewhere.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Signed-off-by: Tigerblue77 <37409593+tigerblue77 at users.noreply.github.com>
Closes #19631
contrib/lutok: remove autotools generated files
These files provide no value in the FreeBSD tree proper and change
frequently, depending on what machine I generate the release tarball on
(and what versions of autotools are on the host). Nuke the autogenerated
files to avoid bloating commit history/the tree.
MFC after: 3 days
Requested by: Benjamin Jacobs <freebsd at dev.thsi.be>
(cherry picked from commit cfe443e1e63dd588fba7eabec553ed5e1c408d1f)
tests: Wait for autotrim to reclaim file vdevs
TXG syncs do not wait for the autotrim thread. Continue syncing until
the vdevs reach the existing size limit, within the existing timeout.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Signed-off-by: Giuseppe Piscitelli <ooonea at gmail.com>
Assisted-by: OpenAI Codex
Closes #19623
sbuf(3): clean up tests
- Update the copyright dates and add "Joao Bonifacio" to the top of
`sbuf_core_test.c`.
- Use `SPDX-Identifier` instead of longform copyright tort.
- Remove `sbuf_test_common.h`: the header was originally added to help
with the 10.x/11.x split, but is no longer needed given that those
releases have been EOLed for multiple years now.
MFC after: 1 week
(cherry picked from commit 3593be37a49e3f5268259bcc2af58cf730b08335)
sbuf(3): increase test coverage
This change adds additional explicit test coverage for the following
sbuf(3) APIs:
- sbuf_clear_flags
- sbuf_get_flags
- sbuf_set_flags
While here, add a missing `sbuf_delete` to `sbuf_drain_ret0_test`: while
it isn't strictly required (the library's state is cleaned up shortly
after the test process ends), tools such as Coverity and LSAN flag
issues with leaked memory. Adding the sbuf_delete(3) call to the test
quells that issue.
MFC after: 1 week
Reviewed-by: ngie
Pull-Request: https://github.com/freebsd/freebsd-src/pull/2367
(cherry picked from commit 642b3d965eb6ef3ecf733950e66fad565a27c967)
sbuf(3): clean up tests
- Update the copyright dates and add "Joao Bonifacio" to the top of
`sbuf_core_test.c`.
- Use `SPDX-Identifier` instead of longform copyright tort.
- Remove `sbuf_test_common.h`: the header was originally added to help
with the 10.x/11.x split, but is no longer needed given that those
releases have been EOLed for multiple years now.
MFC after: 1 week
(cherry picked from commit 3593be37a49e3f5268259bcc2af58cf730b08335)
sbuf(3): increase test coverage
This change adds additional explicit test coverage for the following
sbuf(3) APIs:
- sbuf_clear_flags
- sbuf_get_flags
- sbuf_set_flags
While here, add a missing `sbuf_delete` to `sbuf_drain_ret0_test`: while
it isn't strictly required (the library's state is cleaned up shortly
after the test process ends), tools such as Coverity and LSAN flag
issues with leaked memory. Adding the sbuf_delete(3) call to the test
quells that issue.
MFC after: 1 week
Reviewed-by: ngie
Pull-Request: https://github.com/freebsd/freebsd-src/pull/2367
(cherry picked from commit 642b3d965eb6ef3ecf733950e66fad565a27c967)
ZTS: use native mount records in rootpool tests
Discover Linux ZFS roots and mounted datasets through procfs. Use the
FreeBSD filesystem-type column without changing the SunOS parser.
Clear the per-process exclusion before querying rootpool compression.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Signed-off-by: Giuseppe Piscitelli <ooonea at gmail.com>
Assisted-by: OpenAI Codex
Closes #19647
ZTS: find wipefs through the test command path
Use the wipefs command already exposed by the test environment instead
of a distribution-specific absolute path.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Signed-off-by: ooonea <35407790+ooonea at users.noreply.github.com>
Assisted-by: OpenAI Codex
Closes #19648
contrib/lutok: remove autotools generated files
These files provide no value in the FreeBSD tree proper and change
frequently, depending on what machine I generate the release tarball on
(and what versions of autotools are on the host). Nuke the autogenerated
files to avoid bloating commit history/the tree.
MFC after: 3 days
Requested by: Benjamin Jacobs <freebsd at dev.thsi.be>
(cherry picked from commit cfe443e1e63dd588fba7eabec553ed5e1c408d1f)
build: install NextBSD packages with NextBSD's pkg-static (#609)
The NextBSD repository now carries the NextBSD ABI (NextBSD:27:<arch>,
OSVERSION 2700000), and the build VM's stock pkg refuses it ("wrong
architecture: NextBSD:27:aarch64 instead of FreeBSD:15:aarch64").
Install NextBSD-everything, the pkglist.txt packages and the residue
clean with nextbsd-contrib's pkg-static, the same tool nextbsd-pkg uses,
with ABI=NextBSD:27:<arch> (aarch64 on arm64) and OSVERSION=2700000. The
workflow downloads the amd64 pkg-static from nextbsd-contrib's continuous
release for both build jobs (amd64/arm64 and rpi5); a hand run fetches
it. The FreeBSD:15 ABI pin and the VM's uname -K OSVERSION are gone, so
the image's package database carries the ABI its own pkg computes.
Refs nextbsd/nextbsd-kernel#376
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
contrib/atf: upgrade to 0.26
This new version gets contrib/atf in line with the published version of
the package up on [GitHub][github].
Please note that this release is a major update: it contains several
bugfixes and feature enhancements. Most were already present in the
FreeBSD src repo, but there were a large number of changes made in
addition to what was already present.
MFC after: 1 month
Merge commit '9c78088348bcf1059d82a62bb57a0746309d4312'
(cherry picked from commit 952231086100bed7130212b5425e44ffd732913b)
[github]: https://github.com/freebsd/atf
build: install NextBSD packages with NextBSD's pkg-static
The NextBSD repository now carries the NextBSD ABI (NextBSD:27:<arch>,
OSVERSION 2700000), and the build VM's stock pkg refuses it ("wrong
architecture: NextBSD:27:aarch64 instead of FreeBSD:15:aarch64").
Install NextBSD-everything, the pkglist.txt packages and the residue
clean with nextbsd-contrib's pkg-static, the same tool nextbsd-pkg uses,
with ABI=NextBSD:27:<arch> (aarch64 on arm64) and OSVERSION=2700000. The
workflow downloads the amd64 pkg-static from nextbsd-contrib's continuous
release for both build jobs (amd64/arm64 and rpi5); a hand run fetches
it. The FreeBSD:15 ABI pin and the VM's uname -K OSVERSION are gone, so
the image's package database carries the ABI its own pkg computes.
Refs nextbsd/nextbsd-kernel#376
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
tests/libc: only build brk_test where libc provides sbrk
Replace the exclusion list with an allowlist of the architectures
whose libc exports brk/sbrk: amd64, i386, arm and powerpc.
On aarch64, riscv and loongarch libc does not export those symbols
and the test cannot run, so do not build it there. New architectures
now default to not building the test unless brk support is added.
MFC after: 1 week
Signed-off-by: Xiaoqiang Zhao <zhaoxiaoqiang007 at gmail.com>
Reviewed by: ngie
Differential Revision: https://reviews.freebsd.org/D60357
(cherry picked from commit 8a7df6c58d549bd2eaa5cad30b2ef93c3eca3c18)
