Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Customizing cont.new with stack size

Offen
  • Stimmt etwas nicht?
#156 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
wasm
Bereich
compilers

Rechercherichtung

Start by reviewing the cont.new instruction and the proposal's existing stack-switching semantics. Compare the listed stack-allocation strategies, then determine whether the small-coroutine marker, its minimum stack guarantee, and the well-defined overflow exception can be specified consistently. Done requires an agreed proposal-level design rather than a single localized edit.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

One of the trickiest issues to solve in stack switching is how big a stack to allocate for the new coroutine. Empirically, it has been observed that coroutines' memory requirements are often wildly divergent with some (perhaps most) coroutines only needing a small amount of memory to complete their task.

There are several ways of dealing with this:

  1. use fixed size stacks that are the same size as the default stack.
  2. implement a strategy for automatically growing stacks
  3. allow the user (toolchain) to specify the size of the stack for the new coroutine.

The advantages of these different approaches include:

  1. Simplicity of implementation.
  2. Sensitivity to actual computation requirements; in addition, the default size of a stack can be set to a small value -- allowing an application to have large numbers of suspended computations.
  3. The application author may be the best source of actual knowledge about the expected size of a task. Allowing the toolchain to express this facilitates this.

Each of these also has disadvantages:

  1. Particularly on limited memory platforms (such as mobile devices) there may not be enough address space to accommodate large numbers of large stacks.
  2. Automatically growing stacks is complex to realize (a stack overflow can occur in code that was not compiled for coroutining) and significantly increases the attack surface for security vulnerabilities.
  3. the toolchain may not know how much space to allocate for the stack. In particular, WebAssembly does not expose this information -- for good reasons. In addition, the toolchain may guess incorrectly.

A proposal:

allow a form of coarse grain estimation of the expected size of a coroutine, and throw a well defined exception when the actual computation is too large.

I suggest simply adding a marker to the cont.new instruction that declares that "the coroutine is small". This would allow the engine to allocate a small stack structure for that coroutine.

How small is small?

This may be implementation defined; however, I suggest that a more rigorous approach would be to specify a minimum amount of stack space would be available. This could be expressed in bytes but higher level, engine independent way, would be to state this as a combination of frames and local variables.

This approach would allow toolchains to optimize the overall memory footprint of generated applications whilst also allowing for some large stacks. One might imagine, for example, that when implementing generators most coroutines would be marked as small, whereas the default for green threads would be normal sized stacks.

Vorherrschende Sprache
WebAssembly
Sterne
218
Forks
19
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus WebAssembly/stack-switching

Alle Issues in WebAssembly/stack-switching

Ähnliche Issues

Weitere Issues zu Compilers

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.