18 ms·
Code in ARM Assembly: Registers Explained
- jiri 5y agoIt's just a pity that the article ended just when I was most interested :-)
- saagarjha 5y ago> Passing arrays, structures and other arguments which can’t simply be put into a single register requires a different method, in which a pointer to the data is passed: ‘call by reference‘. Note that small structures will be passed in registers. Here's an example: https://godbolt.org/z/rsGEbefcv https://godbolt.org/z/rsGEbefcv. a and b are 32 bits and passed packed in x0, and c is a long passed in x1.
- pdpi 5y agoIt's also wrong to call this "call (or pass) by reference." Pass by reference and pass pointer by value are different things (here's an example — https://godbolt.org/z/Kv7jPPvnz https://godbolt.org/z/Kv7jPPvnz)
- secondcoming 5y agoA reference is just a pointer but with restrictions enforced by the compiler. ASM-wise, they're totally the same thing. 'Reference' doesn't mean C++'s reference, it means that you pass where the data is, not the data itself. Even Visual Basic had this concept.
- deleted 5y ago[deleted]
- MaxBarraclough 5y agoArgument-passing semantics (evaluation strategies) are something defined by the source language, not by the calling convention of the target architecture/platform. pdpi is right to point out that what the article is describing is not pass-by-reference semantics. Unlike C++, C does not support pass-by-reference (ignoring preprocessor silliness). Passing a pointer by value is not the same thing. edit To be clear, C++ supports both pass-by-value and pass-by-reference. This topic cropped up a year ago: https://news.ycombinator.com/item?id=23553574 https://news.ycombinator.com/item?id=23553574
- pdpi 5y agoYes exactly. I believe Fortran and Perl only do pass by reference, for example. It's not a C++ concept, I only used C++ in that example simply because godbolt.org makes it really easy to show how the language treats the two concepts differently even though they compile to the same thing.
- TheRealKing 5y agoThe Fortran standard is deliberately silent about the passing method. However, virtually all Fortran compilers pass by reference.
- jhgb 5y ago> are something defined by the source language, not by the calling convention of the target architecture/platform In that case perhaps the response should have been "pass-by-reference doesn't exist on machine level", not "pass-by-reference is something different", as the latter would seem to be a category error.
- Koshkin 5y ago> the response should have been "pass-by-reference doesn't exist on machine level" Which would barely make any sense.
- jhgb 5y agoHow come? It would illustrate the notion that to a machine, everything is a value, and that (abstract) references get translated into manipulations of values (and not even always in the same way).
- Koshkin 5y agoBecause "on a machine level" and "to a machine" are two different things (the former referring to human understanding).
- jhgb 5y agoYour example seems too C++-specific. Not all languages are defined in the same way.
- Erlangen 5y agoI am familiar with a small set of programming languages, but they define reference and value passing similarly. * Java: Java spec says "pass by value" * C: pass by value * C++: pass by value and reference(with ref qualifier) * C#: pass by value and reference(with ref keyword) Do you know a language that defines "pass by reference" in a very different way?
- Koshkin 5y agoIn assemblers and C passing by reference and passing by pointer value means the same thing.
- jhgb 5y agoNot sure if all language specs explicitly use the "pass-by-X" terminology but for example ANSI Smalltalk standard says things like "Each argument [of a message send] is a reference to an object." > but they define reference and value passing similarly Well, If all of them have been derived from C++ or designed by people trying to improve on C++, they would be very likely to have the notion defined similarly regardless of how anyone else would use the term, so there's not much surprise there.
- MaxBarraclough 5y agoThey're accepted terms in computer science. They're not specific to any programming language. https://en.wikipedia.org/wiki/Evaluation_strategy https://en.wikipedia.org/wiki/Evaluation_strategy
- jhgb 5y agoI was simply saying that C++ using a certain terminology was a sufficient condition for C++-derived languages to use the same terminology, you wouldn't need a CS-wide definition for this and your small set of language wouldn't allow you to make the inference that such a common definition existed. BTW the page you've linked seems to contradict some of your statements: > so they are typically described as call by value even though implementations frequently use call by reference internally for the efficiency benefits As you seem to be arguing that this is not call by reference you should probably correct the page. EDIT: It also seems that there IS some amount of language specificity anyway, since in another place of the page it says: > "In particular it is not call by value because mutations of arguments performed by the called routine will be visible to the caller. And it is not call by reference because access is not given to the variables of the caller, but merely to certain objects" I'm reasonably sure that the first part would be called "call by value" in C++ even if in context of CLU it wasn't if the usual way of doing the same in C++, namely passing a pointer to an object, were to be used.
- MarkSweep 5y agoYou can also pass structs of floating point or SIMD types by register. They have to be 2-4 elements and all of the same type. These are called HFA (Homogeneous Floating-point Aggregate) and HVA (Homogeneous Short-Vector Aggregate). Source: the Procedure Call Standard for the Arm 64-bit Architecture https://github.com/ARM-software/abi-aa/blob/2021Q1/aapcs64/aapcs64.rst https://github.com/ARM-software/abi-aa/blob/2021Q1/aapcs64/a...
- kps 5y agoMore importantly, it's just wrong. Large objects are not converted to references, they're passed on the stack. ¹ §5.4 https://developer.arm.com/documentation/ihi0055/b/ https://developer.arm.com/documentation/ihi0055/b/
- johndoe0815 5y agoRelated - M1 ARM assembly examples by Alex von Below: https://github.com/below/HelloSilicon https://github.com/below/HelloSilicon
- tyingq 5y ago"Apple reserves X18 for its own use. Do not use this register." Interesting. I wonder why that particular one. It's not exactly in the middle of the range. Maybe they searched for typical existing use and decided that was the least likely to have some conflict?
- monocasa 5y agox16, x17, and x18 are all different env pointers not really available for general use per se in the main ABI. x16 and x17 are used for plt linkage there, x18 is reserved for the system to make use of as it sees fit, at it's leisure. x18's use there seems to have survived into Apple's slightly modified ABI.
- comex 5y agoFor more context, look at the standard ARM ABI spec. Apple’s ABI diverges from the standard one in some places, IIRC, but in this case it’s complying with it: the spec says that X18 (which it calls r18) can be reserved by platforms for platform-specific use. The spec also shows how the registers are divided into several categories, which helps explain the choice of X18: https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aapcs64.rst#general-purpose-registers https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aap...
- regularfry 5y ago"All these registers are yours - except X18. Attempt no MOVing there."
- saagarjha 5y agox18 is the standard platform register. On Darwin 20 and higher Apple pins the Rosetta context to it. When not used, it gets zeroed out on return to userspace in what I assume is a subtle prod to avoid its use.
- gardaani 5y agoIs there a reason for giving registers a different name depending on its value's length (D0 = 64-bit, S0 = 32-bit)? I can never remember which names are mapped to the same register. I've had that issue on x86 and I'll have that issue on ARM. I loved how Motorola 68000 made it simple. Each command had a dot-letter suffix indicating the length: move.b d0, d1
- talideon 5y agoMy guess is that it's some effort to maintain some kind of compatibility with ARM32. Back when I used to write ARM asm, it was the ARM 26/32 days, and it was rXX for all the register named in the APCS. It doesn't seem to be as confusing as the x86 situation anyway: none of the registers are _really_ special purpose on ARM. Here's a link to the details in the ARM64 APCS: https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aapcs64.rst#general-purpose-registers https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aap...
- Someone 5y agoOn 68k, that move writes 8 bits; it doesn’t really write to a 8-bit register. I make that difference because, on many (I think) other systems, such a byte move sign extends the least significant byte in d0 to the width of the target register and writes the full register. Also, on 68k you can only address the least significant word or byte of a register that way. Some CPUs have, say, 8 8-bit registers that can alternatively be treated as 4 16-bit registers (https://en.wikipedia.org/wiki/Intel_8080#Registers https://en.wikipedia.org/wiki/Intel_8080#Registers). On such a CPU, one can write to the top half of a register in a single instruction by writing to the 8-bit register that shares its storage (some RISC CPUs support that by having a separate instruction “load top half of register”)
- pm215 5y agoFor 64-bit Arm FPU registers, the mapping is extremely simple: Q0 is the 128-bit vector register; D0 is the bottom 64 bits of it; S0 is the bottom 32 bits; H0 is the bottom 16 bits; B0 is the bottom 8 bits. Similarly Q1/D1/S1/H1/B1 are all the same underlying register. For 32-bit Arm, unfortunately, things are different: D0 is the bottom half of Q0, and D1 the top half; similarly S0 is the bottom half of D0 and S1 is the top half (and so Q0 is S0 S1 S2 S3, with S3 its most significant 32 bits). This is why "just indicate the length on the insn" wouldn't have worked for 32-bit: there is more than one 32-bit register in each 64-bit register (and some kind of 'high/low' notation would have been annoying when you really do want to just think of it as a collection of 32-bit registers sometimes, especially if your hardware doesn't even have double-precision support!). The 64-bit transition fixed up the awkward overlaid mapping, but retains the notation for the benefit of all the people who were already familiar with the Arm notational conventions for things.
- technicalya 5y agoI thought the article contains something exciting, but excitement ended when I was reading the last lines.
- MarkSweep 5y agoRelated, Raymond Chen is doing a series of articles on the ARM instruction set this month: https://devblogs.microsoft.com/oldnewthing/2021/06/ https://devblogs.microsoft.com/oldnewthing/2021/06/
- mhh__ 5y agoI can recommend his articles to anyone interested in what they cover. It's very common to completely miss the bigger picture, or give an incomplete summary, when talking about processors and their design. If I can name names I've always found Lemire's blog anticlimactic - usually a good summary but not fleshed out until someone else comments with the juicy details.
- saati 5y agoThat's about the deprecated Thumb-2, this article is about ARMv8, they are wildly different.
- GeorgeTirebiter 5y agoSeems to me that 'registers' are just really fast memory locations that get referenced by a 'stunted' address space in order to fit into most instructions. In other words, this is not a conceptual necessity. It exists because it's hard to build HW which can access all memory locations really fast. This hardware limitation leaks into software via hacks like 'registers'. Dealing with this hack is what forced Armv8 to remove PC as R15; "In the A32 and T32 instruction sets, the PC and SP are general purpose registers. This is not the case in A64 instruction set." There is a lot of other HW crud that leaks into sw for dubious reasons. For example, although 'wasteful' if every memory location had tag bits -- hardware enforced -- capabilities would layer naturally. More sophisticated memory protection would be possible. Instead, we have these von Neumann archs hellbent on winning some synthetic benchmark. Will the computer-using community ever demand some sacrifice in overall potential "adds-per-second" to enable better security and to support better abstractions? Sadly, I doubt it. Even Risc-V is a baby step.
- saagarjha 5y agoDo note that most processors have a physical register file that is several times larger than what they expose in the ISA. ARM has various mechanisms in flight for tagging; there's already PAC shipping on certain chips and MTE seems like it might be on the horizon. More advanced efforts like Morello are being evaluated, too.
- cesarb 5y ago> Seems to me that 'registers' are just really fast memory locations that get referenced by a 'stunted' address space in order to fit into most instructions. In other words, this is not a conceptual necessity. It exists because it's hard to build HW which can access all memory locations really fast. Registers are unavoidable. Even if you could directly address the whole memory space on every instruction, even if it was all "really fast", the hardware would still need to read the input operands from memory into internal registers, and store the result into an internal register before writing to memory.