From: Johnny Richard <johnny@johnnyrichard.com>
To: Carlos Maniero <carlos@maniero.me>
Cc: ~johnnyrichard/olang-devel@lists.sr.ht
Subject: Re: [PATCH olang 4/5] codegen: calculate the variable offset based on symbol type
Date: Sat, 21 Sep 2024 20:56:46 +0200 [thread overview]
Message-ID: <img55sb64rgodvjeq56fp4yih4qai4fgx7ej4h5632vynlnpnh@vvsuc5usbjlf> (raw)
In-Reply-To: <20240921082437.396691-5-carlos@maniero.me>
On Sat, Sep 21, 2024 at 08:25:00AM GMT, Carlos Maniero wrote:
> This is just an initial structure although it still only supporting u32.
>
> Signed-off-by: Carlos Maniero <carlos@maniero.me>
> ---
> src/codegen_linux_x86_64.c | 26 ++++++++++++++++++++++----
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/src/codegen_linux_x86_64.c b/src/codegen_linux_x86_64.c
> index 1fa6c58..415c81b 100644
> --- a/src/codegen_linux_x86_64.c
> +++ b/src/codegen_linux_x86_64.c
> @@ -35,6 +35,9 @@ codegen_linux_x86_64_emit_start_entrypoint(codegen_x86_64_t *codegen);
> static void
> codegen_linux_x86_64_emit_function(codegen_x86_64_t *codegen, ast_fn_definition_t *fn);
>
> +static size_t
> +type_to_bytes(type_t *type);
> +
If we calculate the size during the symbol creation we don't have to
create this logic all over the places. Other backends would reuse the
already preprocessed size in bytes.
> void
> codegen_linux_x86_64_init(codegen_x86_64_t *codegen, arena_t *arena, FILE *out)
> {
> @@ -366,7 +369,7 @@ codegen_linux_x86_64_emit_block(codegen_x86_64_t *codegen, ast_block_t *block)
> codegen_linux_x86_64_emit_expression(codegen, var_def.value);
> }
>
> - codegen->base_offset += 8;
> + codegen->base_offset += type_to_bytes(&symbol->type);
> size_t *offset = arena_alloc(codegen->arena, sizeof(size_t));
> *offset = codegen->base_offset;
>
next prev parent reply other threads:[~2024-09-21 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 8:24 [PATCH olang 0/5] extend unsined integers types (u8, u16, u64) Carlos Maniero
2024-09-21 8:24 ` [PATCH olang 1/5] parser: replace type enum to an struction string id representation Carlos Maniero
2024-09-21 17:59 ` Johnny Richard
2024-09-21 8:24 ` [PATCH olang 2/5] checker: scope: populate symbol's type Carlos Maniero
2024-09-21 18:47 ` Johnny Richard
2024-09-21 21:23 ` Carlos Maniero
2024-09-22 13:46 ` Johnny Richard
2024-09-21 8:24 ` [PATCH olang 3/5] codegen: fix map simbol list type Carlos Maniero
2024-09-21 18:50 ` Johnny Richard
2024-09-21 8:25 ` [PATCH olang 4/5] codegen: calculate the variable offset based on symbol type Carlos Maniero
2024-09-21 18:56 ` Johnny Richard [this message]
2024-09-21 8:25 ` [PATCH olang 5/5] codegen: perform mov instructions based on variable type Carlos Maniero
2024-09-21 8:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-21 19:17 ` [PATCH olang 5/5] codegen: perform mov instructions based on variable type Johnny Richard
2024-09-21 21:30 ` Carlos Maniero
2024-09-22 14:16 ` [PATCH olang 0/5] extend unsined integers types (u8, u16, u64) 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=img55sb64rgodvjeq56fp4yih4qai4fgx7ej4h5632vynlnpnh@vvsuc5usbjlf \
--to=johnny@johnnyrichard.com \
--cc=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