[offload] Fix --libomptarget-nvptx-bc-path in tests (#199382)
PR #198622, which landed as 3383f0d6fe01, causes 272 `libomptarget ::
nvptx64-nvidia-cuda` test fails on my system with:
```
clang: error: bitcode library '/home/jdenny/llvm/build/\./lib/x86_64-unknown-linux-gnu/nvptx64-nvidia-cuda' does not exist
```
This patch fixes that.
doc: Updated mail/roundcube and related packages to 1.6.16
mail/roundcube
mail/roundcube-plugin-enigma
mail/roundcube-plugin-password
mail/roundcube-plugin-zipdownload
mail/roundcube: update to 1.6.16
1.6.16 (2026-05-14)
This is a security update to the LTS version 1.6 of Roundcube Webmail.
It provides fixes to recently reported security vulnerabilities:
* Fix stored XSS/HTML/CSS injection in subject field of the draft restore
dialog, reported by zazy
* Fix CSS injection bypass in HTML sanitizer via SVG <animate
attributeName="style">, reported by wooseokdotkim
* Fix pre-auth SQL injection in virtuser_query plugin via preg_replace
backslash escape bypass, reported by skull
* Fix SSRF bypass via specific local address URLs
* Fix local/private URL fetch bypass when remote resources were not allowed,
reported by Orange Cyberdefense Vulnerability Disclosure Team
* Fix bypass of remote image blocking via CSS var(), reported by Geame
* Fix pre-auth arbitrary file delete via redis/memcache session poisoning
bypass, reported by valent1
[24 lines not shown]
databases/cego: update 2.54.23 -> 2.54.25
- btree dump implementation to CegoAction::execDumpBTree
- cleanup of dump statements ( moved dump table / btree statements from
CegoAdm.def to Cego.def ).
Dump still supported for table objects
- In CegoFunction::evalFieldValue, case USERDEFINED,
removed cout debugging statements
- A recovery issue occured when using user function is expression list
for update operations. For expressions containing user functions,
the values for CegoQueryManager and tabSetId have to be setup explicit,
since this is not done by redo log decoding. The corresponding setup
method setQueryManager has been added for all involved classes
( CegoExpr, CegoTerm, CegoFactor, CaseCaseCond, etc )
- new global variable CegoFieldValue::__recoveryTS has been introduced.
During transaction recovery, this variable is setup to the
corresponding recovery timestamp. So the constant datatime value
sysdate is setup to the current recovery timestamp value
( otherwise the current timestamp is used )
[10 lines not shown]
[MC] Create new MCScheduleOptions cl::opt category (#198746)
This patch creates a new cl::opt category for MCSchedule options. It
enables tools to filter MCSchedule options based on category.
Specifically, llvm-mca now filters them in, and displays them under
`--help-hidden`, which wasnt the case before.
[InstCombine] Fix vector_reduce_mul(sext <n x i1>) for odd n. (#199401)
Before this patch, instcombine folded
vector_reduce_mul(sext (<n x i1> val))
to
zext(vector_reduce_and(<n x i1> val)).
But this is incorrect when n is odd: The result of the reduction is -1,
not 1.
After this patch we only do this fold when n is even.
This bug was found by a large run of Opus 4.7 looking for bugs in LLVM.
Fix missing 'compatible' string NUL termination in case the compatible
string is => 32 bytes, which caused an out-of-bounds read later on in
the code path:
- Mimic apliic(4), which uses malloc instead of a fix-width array for
the compatible string.
- Also set 'ia_namelen', which should enable parsing of a secondary
compatible string, if it exists.
ok jca@
net/intel-em-kmod: unbreak for FreeBSD 15+
FreeBSD 15 introduced some incompatible KAPI changes.
Apply some patches to this code dated back 2019.
This fixes build, so PORTREVISION not changed.
The change is run-tested using 15.0-RELEASE and 82574L-based
network adapters. Compile-tested only for recent 16.0-CURRENT.
callout(9): tweak
Don't change the name of the argument when explaining callout_pending.
Don't do manual "code hilighing".
Format the paper reference properly (and add missing information).
[ConstantFolding] Handle large exponents in ldexp (#199309)
Previously if you passed a constant exponent to llvm.ldexp greater than
the width of `int`, we would silently truncate it to `int` before
using it in scalbn. We'd thus generate the incorrect result.
We now clamp it to fit within int.
This bug was found by a large run of Opus 4.7 looking for bugs in LLVM.
