Update ocaml-cmdliner to version 1.3.0.
v1.3.0 2024-05-23 La Forclaz (VS)
Add let operators in Cmdliner.Term.Syntax (#173). Thanks to Benoit Montagu for suggesting, Gabriel Scherer for reminding us of language punning obscurities and Sebastien Mondet for strengthening the case to add them.
Pager. Support full path command lookups on Windows. (#185). Thanks to @kit-ty-kate for the report.
In manpage specifications use $(iname) in the default introduction of the ENVIRONMENT section. Follow up to #168.
Add Cmd.eval_value' a variation on Cmd.eval_value.
v1.2.0 2023-04-10 La Forclaz (VS)
In manpage specification the new variable $(iname) substitutes the command invocation (from program name to subcommand) in bold (#168). This variable is now used in the default introduction of the EXIT STATUS section. Thanks to Ali Caglayan for suggesting.
Fix manpage rendering when PAGER=less is set (#167).
Plain text manpage rendering: fix broken handling of `Noblank. Thanks to Michael Richards and Reynir Björnsson for the report (#176).
Fix install to directory with spaces (#172). Thanks to @ZSFactory for reporting and suggesting the fix.
Fix manpage paging on Windows (#166). Thanks to Nicolás Ojeda Bär for the report and the solution.
[CIR] Support CoyieldExpr in emitLValue (#232298)
In `CIRGenFunction::emitLValue`, `Expr::CoyieldExprClass` previously
called `errorNYI`. When a coroutine yields an expression whose
`yield_value()` returns an awaiter whose `await_resume()` returns an
lvalue reference (for example, `int &r = co_yield 0;` or `(co_yield 0) =
42;`), Clang evaluates the `CoyieldExpr` as an lvalue. The resume
pointer is spilled and reloaded across `cir.await` to maintain MLIR SSA
dominance in the parent scope.
Fixes #232233.
HBSD: Resolve merge conflict
Use FreeBSD's generated distinfo. The only thing that changed was the
timestamp, anyways.
Signed-off-by: Shawn Webb <shawn.webb at hardenedbsd.org>
math/py-triangle: unbreak with Python 3.13
math/py-triangle 20230923 does not build with Python 3.13. In the
Python 3.13 exp-run of 2026-07-13 it failed in the build phase:
triangle/core.c:31640:67: error: too few arguments to function call, expected 6, have 5
31638 | ret = _PyLong_AsByteArray((PyLongObject *)v,
31639 | bytes, sizeof(val),
31640 | is_little, !is_unsigned);
Log: https://pkg-status.freebsd.org/gohan06/data/150amd64-default-foo/2026-07-13_05h37m51s/logs/errors/py313-triangle-20230923_1.log
The release ships a core.c generated by an older Cython, which calls
_PyLong_AsByteArray() with the old argument list; Python 3.13 added a
sixth argument.
20250106 (uploaded to PyPI 2025-01-07) is the next release; the only
change is that the bundled core.c was regenerated with Cython 3.0.11.
The patch updates the port to it.
[23 lines not shown]
ObsoleteFiles.inc: Add moved certificates
These two moved from trusted to untrusted.
Fixes: 21ac4761428c ("ObsoleteFiles.inc: Add dropped certificates")
[SLP]Fix loop scale of reduction roots and cost of vector GEPs
The buildvector root of a reduction was costed once per tree, while
the reduction itself was scaled by the loop trip count.
Vector GEPs with different bases are not folded into the gather or
scatter addressing, the scaled indices are added to the bases.
Part of #227393.
Assisted-by: Cursor
Reviewers:
Pull Request: https://github.com/llvm/llvm-project/pull/233972
NAS-144662 / 25.10.8 / Do not include leading/trailing whitespaces in `rclone` init config value (by themylogin) (#20032)
Two different users had Backblaze B2 keys with leading whitespaces
stored in the database (probably, that's how due to how B2 keys are
copied from their webpage).
In old config generator it was never a problem:
```
key = xxx
```
is parsed as '{"key": "xxx"}` (even though there are two white spaces
between = and xxx)
With new generator, it became a problem:
```
key = """ xxx"""
```
is parsed as '{"key": " xxx"}`
[6 lines not shown]
NAS-144662 / 27.0.0 / Do not include leading/trailing whitespaces in `rclone` init config value (by themylogin) (#20033)
Two different users had Backblaze B2 keys with leading whitespaces
stored in the database (probably, that's how due to how B2 keys are
copied from their webpage).
In old config generator it was never a problem:
```
key = xxx
```
is parsed as '{"key": "xxx"}` (even though there are two white spaces
between = and xxx)
With new generator, it became a problem:
```
key = """ xxx"""
```
is parsed as '{"key": " xxx"}`
[6 lines not shown]
[llvm][GlobalOpt] Preserve COMDATs for Dead GVs (#222720)
* This PR preserves COMDATs under the following case:
* Dead functions
* Even though a function is dead, its COMDAT may still be referenced.
* On ELF, it is valid to have a "freestanding" COMDAT.
* _Note_: AFAIK this change in behavior should have no consequences for
ELF (or MachO) though someone with more experience can chime in. As
there wasn't prior precedent to having platform specific code in
`GlobalOpt`, for now I've refrained from guarding this logic to be
specific to COFF.
* On COFF, this results in an Associative COMDAT error: `LLVM ERROR:
Associative COMDAT symbol 'foo' does not exist.`
* Replaces https://github.com/llvm/llvm-project/pull/220737 to create
stacked PR.
[clang-format] Fix first-line width calculation for CRLF multiline tokens (#228752)
The first-line width of a multiline token is calculated from the text
before the first `LF`. For `CRLF` input, this includes the preceding
`CR`, which is counted as an extra column and can change wrapping at the
column limit.
Exclude the trailing `CR` when measuring the first-line width while
preserving the token text. Add a regression test covering `LF` and
`CRLF` multiline raw strings whose first line, including the preceding
code, exactly fits the column limit.
Fixes #224571
Assisted-by: Codex
