cskk: update to 4.0.0
Major version was upgraded as there are breaking changes in the
configuration file.
Added
* Conversion trigger keys can be changed by adding `composition_triggers`
array in rules file. Symbol keys (ex. exclam) other than A-Z keys can be
specified as conversion trigger keys.
Refer to docs/henkan-trigger-extension.md in details.
Changed
* Breaking Change for rule authors: If `[option] composition_triggers` is
omitted in rules file, any key does not trigger headword input state (▽
mode).
For using custom rules, `composition_triggers` needs to be added to
`[option]` section (at least specify 26 characters "A" ~ "Z").
[2 lines not shown]
Reland "[libc] Implement clone(2) and use it in thread spawning" (#225384)
This commit reverts 35006688eb78eb5b601e282d21701f430d737888/#225111,
reapplying 9028ff14b18ea678683a4960306051044160bb67/#224257. It fixes an
error in risc-v assembly (forgot to adjust for constant renaming).
The original commit message was:
This patch implements an internal clone syscall wrapper and uses it both
to implement the public clone(2) entry point and to spawn new threads in
libc's thread implementation.
Previously, thread creation in thread.cpp invoked the raw SYS_clone
syscall directly, requiring target-specific inline assembly or register
variables and subtle tricks with __builtin_frame_address to pass
arguments to start_thread in the newly spawned thread.
By introducing an inline assembly clone wrapper that sets up func and
arg on the child stack and jumps to the entry function upon clone
[22 lines not shown]
NAS-143065 / 27.0.0-BETA.1 / Validate VM and container UUIDs the way libvirt does (#19824)
`UUIDv4String` did neither thing its name implies. `uuid.UUID(value,
version=4)` overwrites the version and variant bits on a throwaway
object rather than asserting them, so nothing was ever checked; and the
validator returned the caller's original string, so every spelling of a
UUID was stored verbatim. Two things went wrong as a result.
The stored string is the libvirt identity — it is written to both
`<name>` and `<uuid>` of the domain XML, and domains are looked up by
name. Because the create-time uniqueness check was a datastore filter,
i.e. SQL `=` against a BINARY-collated column, two rows spelling one
UUID differently both got in. Domains are only defined at start, so
nothing went wrong until the second one was started, at which point
libvirt refused it while quoting the first row's uuid. `uuid` is
immutable after creation, so that row cannot be repaired.
Separately, Python and libvirt disagree about what a UUID even looks
like. `uuid.UUID()` strips braces and a `urn:uuid:` prefix; libvirt's
[31 lines not shown]
NAS-143065 / 27.0.0-BETA.1 / Validate VM and container UUIDs the way libvirt does (#19824)
## Problem
`UUIDv4String` did neither thing its name implies. `uuid.UUID(value,
version=4)` overwrites the version and variant bits on a throwaway
object rather than asserting them, so nothing was ever checked; and the
validator returned the caller's original string, so every spelling of a
UUID was stored verbatim. Two things went wrong as a result.
The stored string is the libvirt identity — it is written to both
`<name>` and `<uuid>` of the domain XML, and domains are looked up by
name. Because the create-time uniqueness check was a datastore filter,
i.e. SQL `=` against a BINARY-collated column, two rows spelling one
UUID differently both got in. Domains are only defined at start, so
nothing went wrong until the second one was started, at which point
libvirt refused it while quoting the first row's uuid. `uuid` is
immutable after creation, so that row cannot be repaired.
Separately, Python and libvirt disagree about what a UUID even looks
[32 lines not shown]
[orc-rt] Use the Error matchers in ConnectionSpecTest (#225603)
Use the Error matchers introduced in 72aeee3df1 to clean up error checks
in ConnectionSpecTest.
py-astropy: remove _compiler.c from PLIST
I guess some dependency update is to blame that it's not installed
any longer, but I don't know which one.
Bump PKGREVISION.
[clang][bytecode] Fix null ptr upcasts adding offset (#224873)
Previously, this was applying the offset it would for non-null pointers,
but null pointers should always cast to a null pointer result.
Fixes https://github.com/llvm/llvm-project/issues/224869
config: housekeeping on curl options
In 8a466bb9360 we disable LIBSSH2, but need to reasses if this
still makes sense or whether libssh2 is pulled into the binary
packages anyway via another source.
[orc-rt] Add Windows virtual memory support (#224521)
Adds Windows virtual-memory support for ORC-RT
Also adds a small Windows error helper that converts GetLastError()
results into ORC-RT Error values with the corresponding system message.
Turns back on all the memory tests for windows.
[RISC-V][MC] Update ELF streamer ArchString when emitting RISCVAttrs::ARCH
During LTO, the TargetMachine subtarget is initialized with the linker's
default CPU (e.g. `generic-rv64`, `rv64i2p1`), while
RISCVAsmPrinter::emitStartOfAsmFile() reconstructs the module's actual ISA from
the `riscv-isa` module flag and emits RISCVAttrs::ARCH via
RISCVTargetELFStreamer::emitTextAttribute(). Previously only
RISCVAsmParser::parseDirectiveAttribute() called setArchString() after
emitTextAttribute(RISCVAttrs::ARCH, ...), so direct object emission bypassed
the update and tagged `.text` with `$xrv64i2p1` instead of the module's
full architecture string.
Move the setArchString() call into RISCVTargetELFStreamer::emitTextAttribute()
when emitting RISCVAttrs::ARCH so both `.attribute arch` and
RISCVTargetStreamer::emitTargetAttributes() update the active mapping symbol
ISA.
This commit was created with the help of AI tools
