sysutils/logstash93: New port version 9.3.1
Server-side data ingestion and transformation tool (9.3.x version).
Release Notes:
https://www.elastic.co/docs/release-notes/logstash#logstash-9.3.1-release-notes
PR: 293760
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
[MLIR][XeGPU] Fix -Wunused-variable on non-assertions builds
Inline a variable and mark one [[maybe_unused]] so that we do not get
warnings with recent clang in such configurations.
sysutils/logstash92: Update 9.2.3 => 9.2.6
Release Notes:
https://www.elastic.co/docs/release-notes/logstash#logstash-9.2.6-release-notes
Improve port:
- Replace PORTVERSION with DISTVERSION.
- Add LOCAL/vvd/elastic to MASTER_SITES for those who can't download due
to the HTTP error "Forbidden 403".
- Sort USES.
- Adjust JAVA_VERSION to supported LTS 25, 21 and 17.
- Parametrize "logstash" with "${PORTNAME}".
- Adjust CONFLICTS.
- Fix warnings from portclippy.
- Add possibility to use custom user/group.
- Replace RM of bundled JDK and *.bat files with
EXTRACT_AFTER_ARGS=--exclude.
- Merge CHMODs.
- Replace %%PREFIX%% with %%LOCALBASE%% in rc.d script - bash installed
[5 lines not shown]
sysutils/logstash91: Update 9.1.9 => 9.1.10
Release Notes:
https://www.elastic.co/docs/release-notes/logstash#logstash-9.1.10-release-notes
Improve port:
- Replace PORTVERSION with DISTVERSION.
- Add LOCAL/vvd/elastic to MASTER_SITES for those who can't download due
to the HTTP error "Forbidden 403".
- Sort USES.
- Adjust JAVA_VERSION to supported LTS 25, 21 and 17.
- Parametrize "logstash" with "${PORTNAME}".
- Adjust CONFLICTS.
- Fix warnings from portclippy.
- Add possibility to use custom user/group.
- Replace RM of bundled JDK and *.bat files with
EXTRACT_AFTER_ARGS=--exclude.
- Merge CHMODs.
- Replace %%PREFIX%% with %%LOCALBASE%% in rc.d script - bash installed
[5 lines not shown]
[clang][ssaf] Fix missing library dependency (#186496)
Caused by #186442
Similar to #186475
Addresses:
https://github.com/llvm/llvm-project/pull/186475#issuecomment-4057355167
```
/usr/bin/ld: tools/clang/unittests/ScalableStaticAnalysisFramework/CMakeFiles/ClangScalableAnalysisTests.dir/ASTEntityMappingTest.cpp.o: undefined reference to symbol '_ZN4llvm3omp27isAllowedClauseForDirectiveENS0_9DirectiveENS0_6ClauseEj'
/usr/bin/ld: /home/botworker/builds/openmp-offload-amdgpu-runtime-2/llvm.build/lib/libLLVMFrontendOpenMP.so.23.0git: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
```
[lldb] Preserve TargetSP in Platform module lookup (#186323)
[lldb] Preserve TargetSP in Platform module lookup
When `Platform::GetRemoteSharedModule` resolves a module specification
by calling `GetModuleSpec` on
the process, the target context (`TargetSP`) is lost. This happens
because the underlying process plugin populates a new `ModuleSpec`
object that does not inherit the target context.
This causes failures in subsequent symbol resolution steps. For example,
when `ModuleList` relies on the `TargetSP` to query target-specific
settings like `target.exec-search-paths` and
`target.symbols-search-paths`, the lookup fails
because `TargetSP` evaluates to null. This prevents LLDB from finding
local unstripped libraries.
This commit fixes the issue by transferring the target context from the
original `module_spec` over to the `resolved_module_spec` before
[9 lines not shown]
[AArch64][llvm] Rewrite the TLBI multiclass to be much clearer (NFC)
The `tlbi` multiclass is really doing four jobs at once: base TLBI,
synthesized nXS, optional TLBIP, and synthesized TLBIP nXS. Also,
`needsreg` and `optreg` are really just a 3-state operand policy in
disguise. Likewise, the PLBI multiclass has this same issue.
Change `needsreg` and `optreg` into a combined fake enum, so it's
clearer whether the instruction takes no register operand, a required
register operand or an optional register operand.
This improves on my original change 66e8270e8.
[X86] lowerV4F32Shuffle - don't use INSERTPS if SHUFPS will suffice (#186468)
If we have 2 or more undef/undemanded elements, the INSERTPS replaces
those with explicit zero'd elements which can cause infinite loops later
on in shuffle combining depending on whether we demand those elements or
not.
I'll try to improve the (minor) v2f32 regressions in a follow up, but I
need to fix the infinite loop first.
Fixes #186403
[LifetimeSafety] Fix false positives for pointers in loops (#182368)
When a pointer and its pointee die in the same loop scope, the back-edge
makes the pointer appear live at the pointee's `ExpireFact`, causing a
spurious use-after-scope warning. The origin's loans and liveness are
cleared at `LifetimeEnds` via `ExpireFact`, preventing the checker from
reporting against an origin whose variable is already dead.
Fixes: #169548
rtld-elf: Remove stray _exit prototype for aarch64
It's not clear why this is here. It's existed since the very first
version of rtld-elf for aarch64 but has never been used, and anything
actually using exit or _exit should be using rtld_libc.h's #define that
aliases them to __sys_exit.
Fixes: 047c6e3ae6ab ("Add the arm64 code to the runtime linker. It's not able to be built as we still need libc_pic for a few things, but this is expected to be ready soon.")
[LLDB][NativePDB] Add support for `S_REGREL32_INDIR` (#186124)
In #183172, I added support for reading `S_REGREL32_INDIR` records. This
adds support in LLDB. The record is emitted by MSVC for structured
bindings and in the compiler generated coroutine stubs.
It describes a location at `*(Register + Offset) + OffsetInUdt`.
Equivalent to
```
DW_OP_breg{reg} {Offset}
DW_OP_deref
DW_OP_plus_uconst {OffsetInUdt}
```
LLVM doesn't create this record - it only creates `S_LOCAL`s for local
variables. We'll probably need `S_DEFRANGE_REGISTER_REL_INDIR` for this
- should be simple to figure out the structure, but I haven't seen that
record emitted yet.
[AArch64][llvm] Rewrite the TLBI multiclass to be much clearer (NFC)
The `tlbi` multiclass is really doing four jobs at once: base TLBI,
synthesized nXS, optional TLBIP, and synthesized TLBIP nXS. Also,
`needsreg` and `optreg` are really just a 3-state operand policy in
disguise.
Change `needsreg` and `optreg` into a combined fake enum, so it's
clearer whether the instruction takes no register operand, a required
register operand or an optional register operand.
This improves on my original change 66e8270e8.
[AMDGPU] Fix setreg handling in the VGPR MSB lowering
There are multiple issues with it:
1. It can skip inserting S_SET_VGPR_MSB if we set the mode via
piggibacking. We are now relying on the HW bug for correct
behavior. If/when the bug is fixed lowering will be incorrect.
2. We should just unconditionally update MSBs if offset allows it.
We shall set correct bits and keep the rest of the immediate
(that is done). There is no reasonable way for an user to change
MSBs nor does it do anything good to set it with SETREG and then
immediately overwrite with S_SET_VGPR_MSB.
3. Current implementation assumes that offset in the mask is always
zero, which is not true.
4. Redundand mode changes created as seen in the
hazard-setreg-vgpr-msb-gfx1250.mir.
5. Decoding of the immediate was also wrong with non-zero offset.
With uncoditional immediate update most of time and not relying on
[11 lines not shown]
i6300esbwd: Set error appropriately on event
Per the watchdog driver contract, if the driver successfully arms the
watchdog it must set error to 0, and if it's unable to arm the watchdog
it must leave error alone.
Sponsored by: Hewlett Packard Enterprise
