From: Carlos Maniero <carlos@maniero.me>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Carlos Maniero <carlos@maniero.me>
Subject: [PATCH olang 0/5] fix multiple variables
Date: Sat, 21 Sep 2024 01:12:52 +0000 (UTC) [thread overview]
Message-ID: <20240921011234.191248-1-carlos@maniero.me> (raw)
The expressions in x86 performs stack instructions which was causing
conflicts with the space that was reserved for variables.
This patchset ensures that theses instructions no longer messes with the
stack.
Carlos Maniero (5):
map: add function to retrieve all key-value pairs
scope: make scope a bi-directional tree
ast: checker: add function scope
codegen: reset variable offset on block leave
codegen: preserve function's variable stack location
src/ast.h | 1 +
src/checker.c | 1 +
src/codegen_linux_x86_64.c | 47 ++++++++++++++++++-
src/map.c | 17 +++++++
src/map.h | 10 ++++
src/scope.c | 14 ++++++
src/scope.h | 2 +
.../tests/0025_var_definition_nested.ol | 35 ++++++++++++++
tests/unit/map_test.c | 30 ++++++++++++
9 files changed, 156 insertions(+), 1 deletion(-)
create mode 100644 tests/integration/tests/0025_var_definition_nested.ol
base-commit: cb4b63f5879862d2f8282382128995d4e6eff76c
--
2.34.1
next reply other threads:[~2024-09-21 1:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 1:12 Carlos Maniero [this message]
2024-09-21 1:12 ` [PATCH olang 1/5] map: add function to retrieve all key-value pairs Carlos Maniero
2024-09-21 1:12 ` [PATCH olang 2/5] scope: make scope a bi-directional tree Carlos Maniero
2024-09-21 1:13 ` [PATCH olang 3/5] ast: checker: add function scope Carlos Maniero
2024-09-21 1:13 ` [PATCH olang 4/5] codegen: reset variable offset on block leave Carlos Maniero
2024-09-21 1:13 ` [PATCH olang 5/5] codegen: preserve function's variable stack location Carlos Maniero
2024-09-21 1:13 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-21 1:25 ` [PATCH olang 0/5] fix multiple variables Johnny Richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240921011234.191248-1-carlos@maniero.me \
--to=carlos@maniero.me \
--cc=~johnnyrichard/olang-devel@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox