<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 4/16/22 22:06, Jin-oh Kang wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMnQwqV-5Hq2Lgn15jpBuFU=SwGxUNwB5=NUGVMZy2bPv8nGjw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Apr 17, 2022, 3:59
AM Jin-oh Kang <<a
href="mailto:jinoh.kang.kr@gmail.com" rel="noreferrer
noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">jinoh.kang.kr@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">On Tue, Apr 12,
2022, 5:59 PM Paul Gofman <<a
href="mailto:pgofman@codeweavers.com"
rel="noreferrer noreferrer noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">pgofman@codeweavers.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div dir="ltr">I don’t think this complication
worth it. What we would like to save is address
space on 32 bit, but we can’t (before running 32
on 64 of course where this stack will be on 64
only). We apparently need to reserve address
space for stack at once, so it has the space to
grow, and then growing would only mean saving
committed pages.</div>
</div>
</blockquote>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Maybe allocate extra stack only for
function calls that might need it? Something like
this: <a
href="https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntddk/nf-ntddk-keexpandkernelstackandcallout"
rel="noreferrer noreferrer noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntddk/nf-ntddk-keexpandkernelstackandcallout</a></div>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">There's also <a
href="https://github.com/gcc-mirror/gcc/blob/master/libgcc/config/i386/morestack.S"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/gcc-mirror/gcc/blob/master/libgcc/config/i386/morestack.S</a>,
which is used by gcc -fsplit-stack, but we might need
something more portable.</div>
<div dir="auto">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<blockquote type="cite">
<div dir="ltr">
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<p>Will that work with existing host libraries which actually use
the stack and are supposed to be be compatible with this split
stack mechanics if we do something like that?<br>
</p>
</body>
</html>