[yaml2obj][MachO] Fix byte order of the indirect symbol table (#205044)
This is a follow-up of PR #203680 that added the test case
`linkedit-alignment.test`, which currently fails on big-endian buildbots
(see: https://lab.llvm.org/buildbot/#/builders/98/builds/3084 and
https://lab.llvm.org/buildbot/#/builders/114/builds/906).
The failure seems to be on `yaml2obj`, where `writeDynamicSymbolTable`
emits an indirect symbol table in host byte order rather than the
specified object's byte order (i.e. the `IsLittleEndian` field value).
This PR adds the missing swap and a regression test that round-trips all
endian-sensitive fields with both endianness values.
openimageio: updated to 3.1.14.1
3.1.14.1
Note: This patch release only fixes a build break, which is only encountered if relying on the "auto-build" of dependency OpenColorIO if you don't already have it able to be found on your system. If you aren't encountering this problem, you do not need to upgrade from 3.1.14.0.
appstream: updated to 1.1.3
Version 1.1.3
Features:
* Officially support & read JXL images for icons, validate permitted filetypes
* meson: Allow disabling command-line tools
* news-convert: Recognize "=" as release block header
* news-convert: Handle extra linebreaks better and add support for issue-blocks
* compose: Create content hashes with Blake3 instead of MD5
* Update static data for category and license additions
* validator: Tags without namespace are an error
Specification:
* docs: Convert to Docbook 5
Bugfixes:
* yaml: Ensure certain values are always explicitly emitted as strings
* Never emit usertags that are missing a namespace
[8 lines not shown]
[lldb][bazel] Add the Windows process plugin to the bazel build (#203146)
Add a cc_library for the native Windows process plugin
(ProcessWindowsCommon),
gated to @platforms//os:windows, and register it via the dedicated
@LLDB_PROCESS_WINDOWS_PLUGIN@ slot in the generated Plugins.def. This
mirrors the
CMake build, which special-cases ProcessWindowsCommon into that slot so
it is
initialized after all other process plugins but before ProcessGDBRemote.
With the help of claude.
Tested internally at Meta by converting Bazel -> BUCK and confirming
matches working BUCK contents for windows lldb build.
Class for checking floating-point properties
Applicability of a particular transformation to floating-point
expressions may depend on many parameters. Previously these parameters
were mainly represented by fast-math flags, and in some cases they were
supplemented by rounding mode and exception behavior, and all were
passed as separate arguments to the relevant functions. Implementing
more elaborated support of floating-point requires access to other
properties, including function attributes (such as denormal mode or sNaN
support). Passing these parameters as separate arguments is
inconvenient. To address this problem a special class that collects all
the necessary information is introduced in this commit.
The class is a wrapper over an integer value, where various bit fields
represent properties, that transformations may depend on. This allows
instances of the class to be passed by value. It incorporates fast-math
flags and borrows part of the FastMathFlags interface.
This change was intended to be NFC, but in some cases, the behavior
[2 lines not shown]
cd9660: Add various length checks when parsing RRIP extensions
Pass the length of a RockRidge attribute to the handler functions and
validate that length in each handler. If a parsing error is detected,
abort the entire parsing pass.
Reviewed by: des
Differential Revision: https://reviews.freebsd.org/D57136
NAS-141457 / 26.0.0-RC.1 / V-series V2xx front-bay enclosure support
Adds enclosure2.query support for V2xx (V260/V280) front-bay drives,
which are served by a single Broadcom PEX89088 PCIe switch chip
partitioned into two SES VirtualSES enclosures (replacing V1xx's dual
9600w-12i4e SAS HBAs).
Key V2xx differences handled here:
- The two PEX89088 SES partitions advertise the SAME encid (SAS
address), so the V1xx encid-comparison disambiguation fails.
ses_enclosures2 now falls back to inspecting Array Device Slot element
descriptor labels ('slot01'..'slot12' identifies the NVME0 partition;
'slot13'..'slot24' identifies NVME8).
- V2xx slot indexing differs from V1xx: each partition exposes its 12
owned slots at libsg3 element keys 1-12 (NVME0) or 13-24 (NVME8),
with sysfs slot files matching the key 1:1. slot_mappings now branches
by enc.product so the V2xx table is picked for ECStream 4IXGA-SWp/s.
[10 lines not shown]
NAS-141457 / 26.0.0-RC.1 / V-series rear-bay enclosure support via bifurcated NTG SES partition
Adds enclosure2.query support for V-series rear bays (V140, V160, V260,
V280) served by the bay-serving half of the bifurcated PEX89032 NTG
chip. The other half has no drives and is dropped from enclosure2.query
— discriminated by Array Device Slot descriptor labels ('slot01'..'slot04'
identifies the bay-serving partition; '<empty>' identifies the no-drives
half). Both halves share the same vendor / product / encid, so descriptor
labels are the only discriminator.
Changes:
- ses_enclosures2 adds _VSERIES_REAR_PRODUCTS, the
_vseries_rear_partition_owns_bays discriminator, and
_initialize_v_series_rear_enclosures (picks the bay-serving partition,
tags it slot_designation='REAR', drops the no-drives partition).
get_ses_enclosures grows a deferred_rear bucket and dispatches via the
unified _initialize_v_series_enclosures wrapper.
[19 lines not shown]
Merge tag 'i2c-7.2-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux
Pull more i2c updates from Andi Shyti:
"Cleanups:
- generic cleanups in qcom, qcom-cci and pxa, plus core cleanups in
algo-bit and atr
Fixes:
- davinci: clean up cpufreq notifier on probe failure
- imx-lpi2c: suspend the adapter while hardware is powered down
- ls2x-v2: return IRQ_HANDLED after servicing error interrupts
- stm32f7: fix timing calculation accuracy
DT bindings:
- microchip: permit resets
- i2c-mux-pinctrl: update maintainer entry
- i2c-mux-reg: convert bindings to DT schema"
* tag 'i2c-7.2-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux:
[14 lines not shown]
[RFC][CodeGen] Add generic target feature checks for intrinsics
This PR adds target-independent infrastructure for annotating LLVM intrinsics
with required subtarget feature expressions.
It introduces a TargetFeatures string field to intrinsic TableGen records.
TableGen emits an intrinsic-to-feature mapping table.
Both SelectionDAG and GlobalISel now perform this check before lowering target
intrinsics. This allows targets to opt in by annotating intrinsic definitions
directly, rather than adding custom checks during lowering, legalization, or
instruction selection.
This PR uses one AMDGPU intrinsic as an example.
[runtimes] Don't create shared library targets when unsupported
On platforms that don't support shared libraries (e.g. CMAKE_SYSTEM_NAME of
"Generic", used for GPU and other baremetal targets), CMake's
Platform/Generic.cmake sets the global TARGET_SUPPORTS_SHARED_LIBS property to
FALSE. Under CMP0164's OLD behavior (the default, since the runtimes set
cmake_minimum_required(3.20)), CMake silently demotes SHARED library targets to
STATIC archives. libcxx, libcxxabi and libunwind always create their shared
target, so after demotion both the shared and static targets emit e.g.
"libc++abi.a" and Ninja fails with "multiple rules generate ...".
Rather than papering over the collision with a distinct output name, skip
creating the shared library targets entirely when the platform does not support
them, gating on the TARGET_SUPPORTS_SHARED_LIBS property (left undefined on
platforms that do support shared libraries). The few consumers of the shared
targets are guarded with TARGET checks so they fall back to the static library
or are skipped.
Also set policy CMP0164 to NEW so that any future unguarded
[10 lines not shown]
Merge tag 'i3c/for-7.2' of git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux
Pull i3c updates from Alexandre Belloni:
"This cycle, there was a lot of work around the mipi-i3c-hci driver
that also led to improvements of the core. We also have support for a
new SoC, the Microchip SAMA7D65. And of course, there are small fixes
for the other controller drivers.
Subsystem:
- introduce dynamic address reconciliation after DAA
- add preliminary API for hub support
- fixes for dev_nack_retry_count handling
- move hot-join support in the core instead of open coding in
different drivers
Drivers:
- mipi-i3c-hci-pci: DMA abort, recovery and related improvements,
hot-join support, Microchip SAMA7D65 support, fix possible race in
IBI handling
[25 lines not shown]
[lldb][Windows] Remember server's primary stop thread on gdb-remote stops (#203525)
The client kept the previously-selected thread across stops, ignoring
the primary tid from the server in `T<sig>thread:<tid>`.
On Windows, lldb-server halts the inferior by injecting a thread called
`DbgUiRemoteBreakin` whose only job is to execute an int 3. After an
interrupt, the process has `N+1` threads and the new one is what caused
the stop. The server reports that thread as primary, but the client
ignored it and stayed on whichever thread was selected before. In
`TestExpressionInSyscall` that thread is main, paused just past
`NtDelayExecution`'s syscall with a garbage value in the RSI register.
Evaluating an expression there crashes the JIT trampoline.
This patch makes `ProcessGDBRemote::RefreshStateAfterStop` record the
primary tid from the most recent T-packet's `thread:<tid>` and select it
after applying per thread stop infos.
Fixes `TestBreakpointSetRestart` and `TestExpressionInSyscall` with
LLDB_USE_LLDB_SERVER=1.
rdar://180307914
NAS-141445 / 27.0.0-BETA.1 / Convert truecommand plugin to typesafe pattern (#19162)
This commit adds changes to convert the truecommand plugin to the
typesafe pattern, splitting the old compound ConfigService into a lean
GenericConfigService that delegates to a ConfigServicePart with Pydantic
models, while the portal/wireguard/state logic moves into plain
context-first functions and same-process calls use call2. In-process
consumers of truecommand.config (truenas and security) switch from dict
access to typed attribute access.
[runtimes] Avoid duplicate static archive when shared libs are unsupported
After #203504, runtime sub-builds for GPU/baremetal targets are configured
with CMAKE_SYSTEM_NAME=Generic rather than inheriting the host's system
name. CMake's Platform/Generic.cmake sets the global
TARGET_SUPPORTS_SHARED_LIBS property to FALSE, which causes CMake to
silently turn SHARED library targets into STATIC ones.
libcxx, libcxxabi and libunwind always define their shared library target
(gated by EXCLUDE_FROM_ALL) even when *_ENABLE_SHARED is off, and the shared
and static targets share the same OUTPUT_NAME. With the shared target demoted
to a static archive, both targets generate e.g. "libc++abi.a", which Ninja
rejects:
ninja: error: build.ninja:147837: multiple rules generate
lib/amdgcn-amd-amdhsa/libc++abi.a [-w dupbuild=err]
Default the shared library output name to a distinct "-shared" name when the
platform does not support shared libraries, mirroring the existing workaround
[9 lines not shown]
