From: "Carlos Maniero" <carlos@maniero.me>
To: "Johnny Richard" <johnny@johnnyrichard.com>
Cc: <~johnnyrichard/olang-devel@lists.sr.ht>
Subject: Re: [PATCH olang 5/5] codegen: perform mov instructions based on variable type
Date: Sat, 21 Sep 2024 21:30:46 +0000 (UTC) [thread overview]
Message-ID: <D4CA6QLSKVAC.20JTABMHL7JP3@maniero.me> (raw)
In-Reply-To: <dxh3ahdyr3hilf6ptfifmh6jaowkuu27h4m3kbz3hm5co2p47i@i3dg6mvj7hqi>
> Is this necessary? I mean, isn't GAS smart enough to pick the right mov
> instruction based on register size?
>
> If we have to pick the right size mov explicitly, what do you think
> about renaming it to **get_mov_inst_for(size_t)** or something alike to
> express better the intention?
> This is similar to MOV instruction above, I was thinking about naming it
> to **get_accumulator_reg_for(size_t)** or something else like it. What
> do you think? The current name uses the 64bit version of the
> accumulator register.
Sure! We don't really need both you are right. I will drop the mov
function and keep only the accumulator. I like the name you suggested,
I'll rename as well.
next prev parent reply other threads:[~2024-09-21 21:30 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
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 [this message]
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=D4CA6QLSKVAC.20JTABMHL7JP3@maniero.me \
--to=carlos@maniero.me \
--cc=johnny@johnnyrichard.com \
--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