This patch carries forward our aim to remove offset field from qRegisterInfo packets and XML register description. I have created a new function which returns if offset fields are dynamic meaning client can calculate offset on its own based on register number sequence and register size. For now this function only returns true for NativeRegisterContextLinux_arm64 but we can test this for other architectures and make it standard later.
As a consequence we do not send offset field from lldb-server (arm64 for now) while other stubs dont have an offset field so it wont effect them for now. On the client side we already have a mechanism to calculate the offset but a minor adjustment has been made to make offset increment only for primary registers.
Also some tests have been adjusted for this change.
This part seems dubious. It would be better if it were not tied to the architecture, but to the fact that the stub did not provide the register offset for these registers. It would also be better if it was placed together with the rest of the code for computing the register offsets.