-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arm64 Backend Updates #286
base: master
Are you sure you want to change the base?
Conversation
I_BL => { | ||
var target: bool, outgoing: MachCallConv, livepoint = -1; | ||
for (o in a) { | ||
match (o) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like BL
doesn't really fit under the "none" addressing mode. If you're switching over operands, then it's better to encode that into the addressing mode.
@@ -152,6 +152,14 @@ component V3 { | |||
return buf; | |||
} | |||
match (val) { | |||
x: Box<u1> => buf.putd(x.val); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been trying to move the compiler away from using Box<int>
, Box<long>
, etc, to having dedicated value classes, instead of a parameterized class. I think it'd be less error prone to try to use Box
to enforce the bitwidth of immediates. Therefore I think it'd be better to use Box<int>
for now for all integer-sized immediates.
Lots of updates here.