[MC] Avoid arithmetic between different enumeration types. NFC (#228966)
They are deprecated in C++20 and ill-formed in C++26 (P2864R2).
* Make FirstLiteralRelocationKind and FirstTargetFixupKind constants,
fixing code like `FirstLiteralRelocationKind + ELF::R_*`
* Make the MachO section attributes constants, fixing
`MachO::S_COALESCED | MachO::S_ATTR_*` in MC and lld/MachO.
science/PETSc: upgrade to 3.26.0 and add dependencies for Code_Aster
Recent Code_Aster recommand these options:
- HPDDM
- SLEPc (math/slepc) but problem of circular dependency
- SuperLU (math/superlu)
- hypre (science/hypre)
- ml (ML, trilinos-ml: science/trilinos)
. trilinos-ml is deprecated
see https://github.com/trilinos/ML
. Trilinos is not supported
see https://gitlab.com/petsc/petsc/-/work_items/1943
- sowing (textproc/sowing)
Also replace BLAS + BLIS by OpenBLAS,
- use MPI helper,
- don’t build in debug mode by default,
- fix graphical tests.
[4 lines not shown]
www/py-yt-dlp-ejs: uniquify distfiles by architecture
This allows the distfile cache to fit them all.
(cherry picked from commit 51feb4d2eeead150ca88e561c373eb28067de4ef)
cyrus-imapd312: Update to Cyrus IMAPd 3.12.4.
____________________________________________________________________________________________
Cyrus IMAP 3.12.4 Release Notes
Changes since 3.12.3
Security fixes
* CVE-2026-61907: JMAP snooze bypasses destination-mailbox ACL
An authenticated user with insert permissions on another user's snoozed mailbox could cause
insertion of mail to that user's inbox, or any other of their mailboxes whose id was known to
the user, despite having no insert permissions to the target mailbox.
Reported by: Michael Lynch (mtlynch.io).
* CVE-2026-61908: JMAP email-header blob ID out-of-bounds index
An authenticated user could attempt to download a specially crafted JMAP blob ID of the form
H<emailid>-<index>, which could read past the end of the internal blob_headers array during
download, exposing adjacent heap memory.
[136 lines not shown]
Update to 0.000005
Upstream changes:
0.000005 2026-04-17 11:29:35-07:00 America/Los_Angeles
- Require Importer 0.025+ so `use Importer Importer => 'import'` works
(older Importer versions like 0.014 lack 'import' in IMPORTER_MENU,
causing "Importer does not export &import" at load time)
0.000004 2026-04-15 14:34:09-07:00 America/Los_Angeles
- Add havejump() to check if a named jump point is currently set
[NFCI][llvm-jitlink] Return 1 instead of exit(1) on entry point error (#228311)
In main(), if EntryPoint lookup fails, llvm-jitlink was calling
exit(1). Because exit() is noreturn, the stack is not unwound and
destructors for Session S and its associated objects are not run.
LSan detects these in-flight allocations (such as dlsym buffers
in InProcessDylibManager) as memory leaks at atexit, causing
ExecutionEngine/JITLink/x86-64/COFF_directive_alternatename_fail.s
to fail on ASan/LSan buildbots.
Returning 1 from main() allows S and other local variables to be cleanly
destructed before process termination.
For https://github.com/llvm/llvm-project/issues/186534
Fixes https://lab.llvm.org/buildbot/#/builders/169/builds/27104
Log:
https://lab.llvm.org/buildbot/#/builders/169/builds/27104/steps/11/logs/stdio
Assisted-by: Gemini
Update to 3.101
Upstream changes:
3.101 2026-04-13 13:31:24-04:00 America/New_York
- fix auto-using of Log::Fmt::XS, which was straight up broken
3.100 2026-04-01 10:35:56-04:00 America/New_York
- when present, use Log::Fmt::XS for emitting logfmt
- abstract out logfmt tests for use in both Log::Fmt and Log::Fmt::XS
test suites (but don't consider this public yet)
3.013 2025-10-15 10:12:50-04:00 America/New_York
- typo fixes and spec clarifications
3.012 2025-10-14 12:39:48-04:00 America/New_York
- [ BREAKING CHANGE (BARELY) ]
Log::Fmt now includes a formal specification of the logfmt grammar we
implement, as well as a description of algorithmns to correctly
encode strings. The code has been updated to fall in line, meaning:
[4 lines not shown]
[clang] Fix an accepts-invalid related to concepts and parameter packs (#227494)
HashParameterMapping computes the keys of
UnsubstitutedConstraintSatisfactionCache. In a fold expression, it
hashes the current element for every use of the expanded pack. But in
P...[sizeof(P)], P refers to the whole pack, not the current element. So
two checks with the same element at the same position got the same key
even if the indexed pack differs, and the second one used the first
one's result. This accepted e.g.
template <class T> concept two_bytes = sizeof(T) == 2;
template <typename... P>
void f() requires(two_bytes<P...[sizeof(P)]> && ...) {}
void g() {
f<char, short, short>();
f<char, int, short, short, short>(); // P...[sizeof(char)] is int
}
[4 lines not shown]
