-
Notifications
You must be signed in to change notification settings - Fork 571
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
i#2626 AArch64 encoder: Add isz operand and vector ADD to encoder. #3016
Changes from all commits
3b92c2c
3067d3c
eb63f9c
3c57b20
6360288
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1561,6 +1561,16 @@ fd3fffff : str d31, [sp,#32760] : str %d31 -> +0x7ff8(%sp)[8byte] | |
fd481041 : ldr d1, [x2,#4128] : ldr +0x1020(%x2)[8byte] -> %d1 | ||
fd7fffff : ldr d31, [sp,#32760] : ldr +0x7ff8(%sp)[8byte] -> %d31 | ||
|
||
|
||
# ADD (vector) | ||
4e2c856a : add v10.16b, v11.16b, v12.16b : add %q11 %q12 $0x00 -> %q10 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The script There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right, I've aligned the ADD lines. It should be easy to update the generator script to align on a per-opcode basis. |
||
0e2584a5 : add v5.8b, v5.8b, v5.8b : add %d5 %d5 $0x00 -> %d5 | ||
4e7f87c3 : add v3.8h, v30.8h, v31.8h : add %q30 %q31 $0x01 -> %q3 | ||
0e7f87c3 : add v3.4h, v30.4h, v31.4h : add %d30 %d31 $0x01 -> %d3 | ||
4ebd8633 : add v19.4s, v17.4s, v29.4s : add %q17 %q29 $0x02 -> %q19 | ||
0ebd8633 : add v19.2s, v17.2s, v29.2s : add %d17 %d29 $0x02 -> %d19 | ||
4ee9852d : add v13.2d, v9.2d, v9.2d : add %q9 %q9 $0x03 -> %q13 | ||
|
||
# FMOV (general) GPR to FP reg | ||
1ee70220 : fmov h0, w17 : fmov %w17 -> %h0 | ||
1e27012a : fmov s10, w9 : fmov %w9 -> %s10 | ||
|
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.
Is there a rule for how the instructions are ordered in this file? (I think I was following the "Index by Encoding" in our internal web pages at some point...) If it's feasible, it might be good to follow some canonical ordering and mark omissions with a comment. (But perhaps it isn't feasible.)
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.
The neon patterns should currently follow alphabetic order (as on the A64 -- SIMD and Floating-point Instructions (alphabetic order) index page of the public XML ISA spec). That's how the generator script happens to process them, but IMO that makes it easier to read. On second thought, it might be easier to extend to generator script to work by the index page in the future.