corpus.blog
41554 blogs · 4,417,066 posts Claim your blog
Record · corpus.blog/posts/01a0876b-bd2a-7260-bc69-8af4ca465e78

Why don’t we allow stacks to be sparse, instead of forcing them to be contiguous?

Microsoft Developer Blogs · published 7 September 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at devblogs.microsoft.com Wayback capture
0blogs citing
First cited
—
Most recent
—
Rank this month
not ranked
Links from this post
12
Words captured
682

Cited by

No blog we hold has cited this post yet.

Links from this post

Link
Host
Why don’t we just make the entire stack out of guard pages? Read at the source ↗
devblogs.microsoft.com
https://devblogs.microsoft.com/oldnewthing/20260713-00/?p=112528&commentid=144516
devblogs.microsoft.com
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
qualys.com
https://lwn.net/Articles/725832/
lwn.net
Windows stack limit checking retrospective, follow-up Read at the source ↗
devblogs.microsoft.com
https://devblogs.microsoft.com/oldnewthing/20260311-00/?p=112134&commentid=143917
devblogs.microsoft.com
Windows stack limit checking retrospective: arm64, also known as AArch64 Read at the source ↗
devblogs.microsoft.com
https://developers.redhat.com/blog/2017/09/25/stack-clash-mitigation-gcc-background
developers.redhat.com
https://developers.redhat.com/blog/2019/04/30/stack-clash-mitigation-in-gcc-why-fstack-check-is-not-the-answer
developers.redhat.com
https://developers.redhat.com/blog/2020/05/22/stack-clash-mitigation-in-gcc-part-3
developers.redhat.com
https://app.opencve.io/cve/CVE-2026-77658
app.opencve.io
https://devblogs.microsoft.com/oldnewthing
devblogs.microsoft.com