editors/openoffice-devel: Fix with python >= 3.12
Fix build with python >= 3.12.
Since this is only a build fix, and builds with older python versions
are not changed other than an additional BUILD_DEPENDS, no PORTREVISION
bump is necessary.
PR: 292190
Reported by: George Mitchell <george at m5p.com>
[mlir][scf] Skip ops having results with warning in forall-to-for pass (#175926)
Avoid converting scf.forall ops that have results in forall-to-for pass.
Emit a warning instead of failing the pass, so mlir-opt can still
produce output on mixed IR.
Fixes https://github.com/llvm/llvm-project/issues/174319
[LifetimeSafety] Detect dangling references to field members (#176805)
Add support for detecting dangling references to struct fields in the CFG-based lifetime analysis.
The tests now include cases where accessing fields of temporary objects leads to dangling references, which are properly detected.
- Added `VisitMemberExpr` method to the `FactsGenerator` class to handle field member expressions
- Implemented the method to create origin flow facts for field member expressions
- Updated tests to include CFG-based warnings for dangling references to struct fields
- Fixed previously disabled tests that can now detect these issues
Fixes https://github.com/llvm/llvm-project/issues/176144
NAS-139371 / 26.04 / Add support for clustered local SMB accounts (#18057)
This commit adds support for managing clustered accounts database for
SMB users and groups. This is accomplished by wrapping around existing
TDBHandle utils and expanding their functionality so that they also work
with clustered databases. The passdb-related functions now take a
clustered keyword argument, and group-mapping now has alternative
CLUSTERED path. On config change for `stateful_failover` we re-run the
`smb.configure` endpoint to ensure
that accounts are properly inserted into running configuration.
GlobalISel: Use LibcallLowering to get libcall calling conventions (#176837)
0e304e6d9f306ead81fc5177b8a497af0d416a73 converted the name queries,
but missed some of the calling conventions.
[Clang][AMDGPU] Handle `wavefrontsize32` and `wavefrontsize64` features more robustly (#176599)
We should not allow `-wavefrontsize32` and `-wavefrontsize64` to be
specified at the same time. We should also not allow `-wavefrontsize32`
on a target that only supports `wavefrontsize32`, and the vice versa.
[Clang][AMDGPU] Add a Sema check for the imm argument of ` __builtin_amdgcn_s_setreg`
Our backend cannot select the corresponding intrinsic if the imm argument is not a `int16_t` or `uint16_t`, which is not really helpful.
GlobalISel: Use LibcallLowering to get libcall calling conventions
0e304e6d9f306ead81fc5177b8a497af0d416a73 converted the name queries,
but missed some of the calling conventions.
While almost all the libc locks are taken and released in the same
libc call, flockfile() and ftrylockfile() can be called when
single-threaded and then--while 'holding' the lock--the process can
create another thread, resulting in a broken state. Have the
f{lock,trylock,unlock}file() APIs *always* do real locking so the
exposed state is always consistent.
ok dlg@
CodeGen: Use LibcallLoweringInfo for stack protector insertion
Thread LibcallLoweringInfo into the TargetLowering hooks used
by the stack protector passes.
[Clang][AMDGPU] Handle `wavefrontsize32` and `wavefrontsize64` features more robustly
We should also not allow `-wavefrontsize32` and `-wavefrontsize64` to be specified at the same time.
[RFC][Clang][AMDGPU] Emit only delta target-features to reduce IR bloat
Currently, AMDGPU functions have `target-features` attribute populated with all default features for the target GPU. This is redundant because the backend can derive these defaults from the `target-cpu` attribute via `AMDGPUTargetMachine::getFeatureString()`.
In this PR, for AMDGPU targets only:
- Functions without explicit target attributes no longer emit `target-features`
- Functions with `__attribute__((target(...)))` or `-target-feature` emit only features that differ from the target's defaults (delta)
The backend already handles missing `target-features` correctly by falling back to the TargetMachine's defaults.
A new cc1 flag `-famdgpu-emit-full-target-features` is added to emit full features when needed.
Example:
Before:
```llvm
attributes #0 = { "target-cpu"="gfx90a" "target-features"="+16-bit-insts,+atomic-buffer-global-pk-add-f16-insts,+atomic-fadd-rtn-insts,+ci-insts,+dl-insts,+dot1-insts,+dot2-insts,..." }
[13 lines not shown]
