devel/ruby-hoe: update to 4.6.1
4.6.1 (2026-02-23)
1 minor enhancement:
* Added -C dir arg to sow to cd to dir before creating so I can test local
changes easier.
2 bug fixes:
* Fixes for a very buggy rdoc… wtf
* Switch to pp for debug_gem. Long file lists are finally
readable. Gem#to_ruby is ugly as fuck.
devel/ruby-google-protobuf: update to 4.34.0
4.34.0 (2026-02-25)
Ruby
* Drop references to x64-mingw32 since we no longer support Ruby
3.0. (2b927f1)
* Bump gem dependencies (659e0f3)
* Ruby codegen: support generation of rbs files (#15633) (6ebdf85)
* Support Ruby 4.0 (#25051) (93f4eba)
UPB (Python/PHP/Ruby C-Extension)
* Add recursion guards for the following nested messages: (#25807) (c52dcb4)
* Fix breaking change related to upb_c_proto_library and
upb_proto_reflection_library (b0150c0)
* Removed the third_party/upb/upb/bazel directory. (7efbfe1)
* Add conformance tests for utf8 validation. (e8923a8)
[7 lines not shown]
p5-TimeDate: update to 2.34.
2.34 2026-02-27 17:00:48-07:00 America/Denver
* doc: Increase POD coverage
* refactor: extract _build_lookups helper, remove hash-building duplication
* fix: correct language data bugs and minor code review fixes
* Fixup utf8 and add tests
* Use Dist::Zilla for the distro
* rebase: apply review feedback on #52
* fix: uncomment Indian Standard timezone (IST)
* feat: support boost C++ timestamp format (%Y-%b-%d %H:%M:%S.%f)
* fix: correct typos across documentation and comments
* stop using use vars
* rebase: apply review feedback on #49
* Remove limitation from Date::Parse
* Create Arabic.pm
net/bind918: update to 9.18.46
9.18.46 (2026-02-27)
Bug Fixes
* A stale answer could have been served in case of multiple upstream
failures when following CNAME chains. This has been fixed. [GL #5751]
[AArch64][test] Add i256 codegen baseline tests (#183587)
## Summary
Add baseline codegen tests for i256 operations on AArch64:
- `bitcnt-i256.ll`: ctpop, ctlz, cttz, Hamming distance, parity (3 RUN
lines: +neon, +sve, +cssc)
- `cmp-i256.ll`: 8 icmp variants (slt/sgt/sle/sge/ult/ugt/ule/uge) +
select
- `div-i256.ll`: udiv, sdiv, urem, srem, power-of-2, and constant
division
- `mul-i256.ll`: multiply, multiply-by-constant, add, sub, and, or, xor
- `shift-i256.ll`: variable shl/lshr/ashr, constant shifts, narrow (i32)
amounts
These are test-only NFC pre-patches for `__int256` builtin type support
(#182733). i256 is already a valid LLVM IR type; these tests capture the
current baseline codegen. The main PR will update the CHECK lines to
show codegen improvements (e.g., direct libcall routing for
[17 lines not shown]
[ASan] Mark recent integration tests as accordingly for MSVC (#135889)
Both of these tests will cause an unsuccessful pass when using msvc.
`shadowed-stack-serialization.cpp` - XFAIL due to the metadata not being
generated.
`fakeframe-right-redzone.cpp` - UNSUPPORTED due to the optimization
limitations of the msvc compiler.
---------
Co-authored-by: MacGyver Codilla <mcodilla at microsoft.com>
[compiler-rt][CMake] Fix build when specifying --stdlib= (with 2 dashes) (#136111)
You can pass the stdlib argument either as -stdlib and --stdlib - the
previous regex did not account for this however - which caused the build
to fail, as a --stdlib argument would be replaced with a single dash,
causing clang to assume reading from stdin and the build to fail:
clang++: error: -E or -x required when input is from standard input
clang++: error: cannot specify -o when generating multiple output files
The files
[libcxxabi/CMakeLists.txt](https://github.com/llvm/llvm-project/blob/bf6986f9f09f79da38006a83c339226c429bb686/libcxxabi/CMakeLists.txt#L261)
and
[libunwind/CMakeLists.txt](https://github.com/llvm/llvm-project/blob/bf6986f9f09f79da38006a83c339226c429bb686/libunwind/CMakeLists.txt#L257)
account for this by removing --stdlib first.
Co-authored-by: Vitaly Buka <vitalybuka at google.com>
Add -E to limit number of net packets sent/rcvd
Specifying -E n or -E s/r (where s & r can be empty)
limits the number of network packets that will be sent
to n or s (whichever is specified) and the number of
network packets that will be received before exiting to
n (or r). Specifying 0 (or omitting s or r) means no limit
(which remains the default). Either a digit, or '/' is required.
Leading spaces before n or s are permitted, but no others.
It is OK (and meaningless) to specify -E/ -- this is
deliberate to simplify scripting ("-E $ms/$mr") where either
ms or mr (or both) might be absent.
While adding doc for this to nc.1 reword all references to
"illegal" - nothing in the way nc(1) is used should result
in anyone being prosecuted (or not for not using appropriate
arg combinations anyway).
