opcodes/

	* aarch64-opc.c (print_register_offset_address): Call
	get_int_reg_name to prepare the register name.

gas/testsuite/

	* gas/aarch64/ldst-reg-reg-offset.s: Add tests.
	* gas/aarch64/ldst-reg-reg-offset.d: Update.
opcodes/

	* aarch64-tbl.h (aarch64_opcode_table): Replace IMM0 with
	FPIMM0 for fcmeq, fcmgt, fcmge, fcmlt and fcmle.

gas/testsuite/

	* gas/aarch64/fp-const0-parsing.s: New test.
	* gas/aarch64/fp-const0-parsing.d: Likewise.
Add TARGET_WAITKIND_NO_RESUMED support to the RSP.

Makes gdb.threads/no-unwaited-for-left.exp pass.

WIP.

It seems TARGET_WAITKIND_NO_RESUME alone is insuficient for correct
non-stop.

Assume N is the new stop reply for TARGET_WAITKIND_NO_RESUMED, like in
this patch.  Say, traffic like this:

(no thread was resumed before #1)

GDB sends two steps in a row.

 #1 -> vCont;s:555
 #2 <- OK

(555 exits)

 #3 <- %Stop:N   (no more resumed threads left)

 #4 -> vCont;s:666
 #5 <- OK

And now GDB goes and processes #3, and mistakenly believes no thread
is left running on the target, while in fact, 666 is left running.

Sounds like we need something else in addition to
TARGET_WAITKIND_NO_RESUMED.  Maybe thread exit events (active only for
stepped threads, by default, for efficiency).