corecstat(4): Add Goldmont, Goldmont Plus, and Tremont CPU support.
* This should cover Apollo Lake, Denverton, Gemini Lake,
Elkhart Lake, and Jasper Lake models.
* These last Atom CPU cores use the same MSR registers for the same
states as "Core" CPUs.
corepower(4): Add Goldmont, Goldmont Plus, and Tremont CPU support.
* This should cover Apollo Lake, Denverton, Gemini Lake,
Elkhart Lake, and Jasper Lake models.
[X86] Check global size before section kind in isLargeGlobalValue (NFC) (#237015)
Checking a global's section kind can walk its entire initializer,
whereas
checking its size is cheap.
Part of #236952.
Assisted-by: Gemini
libc/fnmatch/rangematch: fix incorrect arguments to memset
strmbs variable is already a pointer, so calling memset on its address
was equivalent to setting the pointer, but the intent was to set the
pointed object.
This was found while debugging an unrelated issue in the same function.
Fixes: af79566b9315
MFC after: 1 week
libc/fnmatch/rangematch: fix uninitialized variable read in a condition
The condition was logically incorrect and could also result in access to
an uninitialized variable. The bug happened because of misplaced
parentheses in the complex condition. There is another very similar
condition in the code and it has the correct placement, so it does not
have the bug. I used it as an example for the fix. Both conditions
came from the same commit af79566b9315.
For me, the bug appeared as a random failure to match a simple pattern
with '[0-9]' in it. The value of the uninitialized variable depended on
the value left on the stack by other code, so the bug appeared only
under very specific conditions.
FWIW, gcc catches and reports the uninitialized variable problem.
clang does it only with -Wconditional-uninitialized but that flag leads
to too many false positives.
I also found a pattern that deterministically reveals the bug in a
[14 lines not shown]
[VPlan] Don't drop poison-generating flags while building VPlans (#245029)
VPSCEVExpander::tryToReuseIRValue dropped poison-generating flags from
reused IR values right away, modifying the IR even if the plan is
discarded. Prefer values that don't need flags dropped, and otherwise
create an in-IR VPExpandSCEVRecipe, leaving it to SCEVExpander instead.
Such recipes may now only be in the epilogue plan, so don't assert they
were expanded for the main plan.
mcsim: Update to version 6.2.0
June 3rd, 2020 - Release of GNU MCSim version 6.2.0.
Version 6.2.0 offers various extensions,
but most notably parallelization of Monte Carlo,
SetPoints and MCMC simulations,
if you have a multi-processor machine and MPI installed.
[llubi] Add support for memcpy/memmove/memset (#245021)
This patch adds support for memcpy/memmove/memset libcalls. Unlike LLVM
intrinsics, passing null pointers or invalid pointers is UB, even if the
length is zero. Calling memcpy w/ equal src and dest pointers is also
UB.
Aided by DeepSeek-V4.1-Flash-1017.
[libc++][random] Implement LWG 3809 and LWG 4014 (#239844)
Summary:
- Implement LWG 3809 by correcting the seed initialization of
`std::subtract_with_carry_engine` for narrow result types.
- Implement LWG 4014 by reducing seed values modulo `2147483563` before
conversion to `uint_least32_t`, preserving the intended behavior for
wider result types.
- Add regression tests covering both defect reports.
Testing:
-
`libcxx/test/std/numerics/rand/rand.eng/rand.eng.sub/seed_result_type.pass.cpp`
[AMDGPU] Keep soft waitcnts unchanged until SIInsertWaitcnts converges
On the first visit to a loop header only the preheader state is known.
A soft waitcnt there (e.g. from a release fence) can have some of its
counters simplified away while another counter keeps the instruction
alive: the fence's own vmcnt(0), a preceding wait.asyncmark, or an
explicit s_waitcnt. The soft waitcnt was then rewritten with the
simplified value and promoted to a hard waitcnt, or merged into a
preceding hard one. When the back edge later brought a pending LDS
store, the original lgkmcnt(0) request was gone, and the s_barrier after
the release fence no longer waited for it.
Treat soft waitcnts as requests that depend on the incoming state: never
merge, promote or rewrite them while the analysis iterates. They are
kept unchanged in DeferredErasures, a hard waitcnt (existing or new)
carries what is needed on each visit, and the soft waitcnts are erased
once the analysis converges. This extends #220357, which did the same
only for soft waitcnts that were simplified away entirely.
[11 lines not shown]
Reland "[clang][CIR] Add tests for SVE RINT{N,P} intrinsics" (#244954)
This relands #241220 and #241236, which were reverted in #244680.
Since AArch64 call conv lowering, which is now the default since
#244014, doesn't have support for SVE, this does the migration with
`-fno-clangir-call-conv-lowering`, which allows these tests to avoid
call conv lowering.
hwpmc: claim stray PMI NMIs on Intel
core2_intr() claims an NMI only when IA_GLOBAL_STATUS shows an
overflow. It re-enables the LAPIC PMC vector before acking the
status bits, so a PMI raised while the handler runs can latch a
second NMI that finds the status already clear. That NMI goes
unclaimed and, with the default machdep.panic_on_nmi, panics the
machine. hwpmc_amd.c already absorbs such NMIs with a per-CPU
nmi_counter.
Give core2_intr() one credit per serviced PMI and spend it on the
next NMI on that CPU that finds no overflow.
Reproduced on a Xeon D-1518 (Broadwell-DE) running system-wide
CPU_CYCLES sampling: the unpatched kernel panicked with "NMI" after
about 47k PMIs. With this change it ran 12.5 hours (485k PMIs),
absorbed 6 empty NMIs, and did not panic.
Sponsored by: Netflix
[2 lines not shown]
www/opengist: Update to 1.16.0
Changes since 1.15.2:
v1.16.0
Security release
This release fixes 13 security vulnerabilities, please update as soon
as possible. Check the breaking changes and the steps after updating
below.
Added
* Gist comments (#855).
Security
* Unauthenticated writes to gists over Git HTTP
[89 lines not shown]
www/ruby-sinatra: update to 4.2.2
Update www/ruby-sinatra, www/ruby-sinatra-contrib and
www/ruby-rack-protection packages to 4.2.2.
4.2.2 (2026-11-17)
* Fix: Require a dot before the domain for leading-dot permitted_hosts in
Rack::Protection::HostAuthorization
- .example.org no longer permits hosts that only end in example.org,
like evilexample.org
* Fix: Do not treat a missing Referer as same-origin when Sec-Fetch-Site
says the request is cross-site or same-site
- Affects RemoteToken, JsonCsrf and RemoteReferrer in Rack::Protection
- Requests with neither header are accepted as before,
allow_empty_referrer still defaults to true
[67 lines not shown]