Auto-assign pull requests to their author
Add a pr_assign_author job so each new pull request is assigned to the
person who opened it. Bot accounts such as dependabot are skipped since
they cannot be assignees.
fix: [CIR] Check only the converted pointer's address space
Limit opaque pointer conversion to its own address space and diagnose unsupported pointee types where their layout is required. Emit type-specific errors for failed pointer conversions.
Validate pointee memory conversion before deriving copy sizes, alignments, or pointer-difference strides from CIR layout. Keep deeper pointee types opaque when their layouts are not needed.
Assisted-by: Codex / GPT-6
[CIR] Reject language address spaces in DirectToLLVM pointer conversion
Reject unlowered language address spaces in pointer types when bypassing TargetLowering. Guard pointer-producing lowerings, including generated patterns, so failed conversions report legalization failures instead of silently selecting address space zero or constructing invalid LLVM operations.
Assisted-by: Codex / GPT-6
[CIR] Propagate initializer type adjustment failures
Reject initializers whose active members have no LLVM representation, including when an enclosing union's storage type is convertible. Propagate recursive adjustment failures before querying data layout or constructing LLVM operations.
Assisted-by: Codex / GPT-6
[CIR] Propagate type conversion failures in DirectToLLVM (#224237)
Propagate failed type and constant conversions through DirectToLLVM so
unsupported types produce legalization failures instead of invalid LLVM
operations or a void function result.
Assisted-by: Codex / GPT-6
[AMDGPU][True16] Use the right 16-bit operand classes in med3 and sub (#233632)
Int16Med3Pat hardcoded VSrc_b16 instead of using the outputSrcType
parameter it already takes, so the true16 instantiations named the
non-true16 operand class for V_MED3_I16_t16_e64 and V_MED3_U16_t16_e64.
The true16 V_SUB_NC_U16_t16_e64 pattern named VSrc_b16 for the same
reason, where VSrcT_b16 is the true16 operand class.
No test changed
Co-authored-by: Claude Opus 5 (1M context) <noreply at anthropic.com>
[lldb] Fix shared cache segment mapping leak (#232370)
`map_shared_cache_binary_segments` never released the dispatch_data
returned by dispatch_data_create_map. SharedCacheInfo also returned
copies of SharedCacheImageInfo, so the extractor cached by
GetExtractor() was dropped and every lookup mapped the image again.
Keep the mappings alive in a DataBuffer that releases them on
destruction, and share a lazily created extractor between copies so each
image is mapped once.
rdar://189874911
Assisted-by: Claude
[AMDGPU][True16] Select V_CNDMASK_B16_t16 for i1 to i16 extensions (#233646)
In real true16 mode an i16 result lives in a VGPR_16, but the zext,
anyext and sext of i1 to i16 patterns selected V_CNDMASK_B32_e64, which
defines a 32-bit register. Add true16 variants selecting
V_CNDMASK_B16_t16_e64 and guard the existing patterns with
NotUseRealTrue16Insts.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply at anthropic.com>
[lldb][Mach-O] Accept zlib-compressed LC_NOTE payloads (#231745)
LC_NOTE payloads such as "process metadata" can be large and compress
well. A compressed payload uses the layout of a GNU .zdebug section: the
magic "ZLIB", the uncompressed size as a big-endian uint64_t, then an
RFC 1950 zlib stream. Uncompressed payloads keep working. Only "process
metadata" reads its payload through this path for now.
Alternatives considered:
- zstd and xz compress better, but neither is available in every LLDB
build.
- libcompression codecs are Darwin-only.
- An ELF Elf64_Chdr has no magic, so detection would be inferred from
the data, which only holds for JSON.
- A separate note name for compressed payloads would make every reader
look for both names.
The size comes from the file, so it is checked against deflate's maximum
[2 lines not shown]
Merge tag 'x86_sev_for_v7.4_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 SEV updates from Borislav Petkov:
- Report in sysfs which SEV confidential computing features are enabled
in the environment so that related components like a SVSM can query
them and do appropriate configuration
- Add support for a new AMD SEV instruction called RMPOPT which can be
used to reduce the performance overhead of doing confidential guests'
page ownership verification and the like. Work by Ashish Kalra
* tag 'x86_sev_for_v7.4_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/sev: Report MSR_AMD64_SEV in sysfs
x86/sev: Do RMP optimizations on SNP guest shutdown
x86/sev: Perform RMP optimizations asynchronously
x86/sev: Initialize RMPOPT configuration MSRs
x86/sev: Disable CPU hotplug while SNP is active
x86/cpufeatures: Add X86_FEATURE_RMPOPT feature flag
Merge tag 'x86_platform_for_v7.4_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 platform updates from Borislav Petkov:
- Remove code for a no-longer supported Technology Systems 5500 board
- Use named initializers for struct acpi_device_id in the OLPC platform
driver
* tag 'x86_platform_for_v7.4_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/platform/olpc: Use named initializers for acpi_device_id
x86/platform: Remove Technology Systems 5500 board
[mlir][Canonicalizer] Preserve analyses when there is no change (#232159)
Call `markAllAnalysesPreserved` when there is no change in `applyPatternsGreedily`.
Assisted-by: gpt 6 luna
[AMDGPU][True16] Use vgpr32_lo16 for fcopysign and sext_inreg results (#233517)
The true16 fcopysign and DivergentSextInreg patterns produce an i16 from
V_BFI_B32_e64 / V_BFE_I32_e64, which define a 32-bit register. Wrap the
result in the vgpr32_lo16 OutPatFrag so the extracted low half is
anchored to a VGPR_32 instead of relying on type inference, and give the
f64 fcopysign source EXTRACT_SUBREG an explicit i32 type.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply at anthropic.com>
Merge tag 'x86_fpu_for_v7.4_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 FPU state updates from Borislav Petkov:
- Document and cleanup the signal frame handling with the goal to allow
process migration between CPUs with different FPU capabilities but
which use only a common set of FPU features, i.e., think
checkpoint/restore (Andrei Vagin)
- Consolidate how XSTATE features are checked by doing them once during
boot with the intent of removing cpu_has_xfeatures(). Latter will
happen in the next cycle (Eric Biggers)
- Other cleanups
* tag 'x86_fpu_for_v7.4_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/fpu: Remove additional remnants of math emulation
x86/fpu: Remove unnecessary checks for X86_FEATURE_FPU
selftests/x86: Add tests for signal frame FPU portability
[13 lines not shown]
Add the WHOLE_DATASET layout to sharing.s3
Before: sharing.s3.create always created a new dataset. The S3 service
wrote s3data/ and .truenas_s3/ on it. There was no way to serve an
existing dataset over S3. Every share and every writing task on a
bucket's dataset was refused unless it was s3data read-only.
Now:
- SharingS3Entry has `layout`: BUCKET (the default, unchanged) or
WHOLE_DATASET. The field is create-only. The update model excludes
it. The v27_0_0 and v28_0_0 models both carry it, because the
change ships in 27.0 too.
- A new `layout` column stores it. The migration is bbce11d3cbd7
under 27.0, as it ships on 27.0. Master gets a merge migration
(9a4e61c0f2d7) that joins it to the 28.0 chain. Existing rows read
as BUCKET.
- A WHOLE_DATASET create uses the dataset named in `dataset`. Nothing
is created, set or written on that dataset. A failed create does not
[26 lines not shown]
cooledit: update to 5.0.6
Version 5.0.6
* Fixed broken Makefile.
Version 5.0.5
* Fix Linux static build on later distributions.
* Missing rxvt terminal escape sequence.
Version 5.0.4
* Fixed rxvt rendering stutter on slow X connections.
* OS/compiler compatibility fixes.
* Filetool extended attribute support for FreeBSD.
Version 5.0.3
* Update to latest unicode NotoSans fonts (✅)
* rxvt automatically reconnects to remotefs when your link goes down
so you don't have to login again.
* Regular-expression search moved to the Onigmo engine for full
[54 lines not shown]
