---
title: "Discussion on \"Designing Memory for My Bytecode VM\" | Hashnode"
description: "Discussion on \"Designing Memory for My Bytecode VM\". The memory layout for my bytecode VM: why instructions and RAM live in separate arrays, and how that maps to real desktop and embedded hardware."
url: "https://hashnode.com/posts/designing-memory-for-my-bytecode-vm/6a7b79a85fd779d934ad0738"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Designing Memory for My Bytecode VM](https://mathijs-frank.hashnode.dev/designing-memory-for-my-bytecode-vm?utm_source=hashnode&utm_medium=feed)

The memory layout for my bytecode VM: why instructions and RAM live in separate arrays, and how that maps to real desktop and embedded hardware.

Aug 11 · 3 min read · mathijs-frank.hashnode.dev  
Read the article

-   [#virtual-machine](https://hashnode.com/tag/virtual-machine)
-   [#vm](https://hashnode.com/tag/vm)
-   [#programming-blogs](https://hashnode.com/tag/programming-blogs)
-   [#compiler](https://hashnode.com/tag/compiler)
-   [#compilers](https://hashnode.com/tag/compilers)
-   [#embedded](https://hashnode.com/tag/embedded)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#game-development](https://hashnode.com/tag/game-development)
-   [#gamedev](https://hashnode.com/tag/gamedev)

## Written by

[Mathijs Frank](https://hashnode.com/@mathijs-frank)

@mathijs-frank · London, UK

  
[View profile](https://hashnode.com/@mathijs-frank)

Sharing low-level systems and performance projects.

Systems engineer, writing build logs on low-level systems and performance projects.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.