From: James Y Knight <jyknight@xxxxxxxxxx> Date: Wed, 10 Jun 2015 10:40:58 -0400 > But separately from the reliability issue, it seems rather > unfortunate that the 'default' sparcv9 and sparc64 routines aren't > actually coded to the base sparcv9 standard instruction set. It > seems like probably the base routines should limit themselves to > normal LDX/STX or LDDF/STDF instructions, and leave things like > LDBLOCKF (which the docs mark CPU-specific, and deprecated, and > potentially to be removed from future chips), for when a specific > processor is targeted. All sparc64 cpus support block loads and stores. There are documents, and then there is reality. Those instructions cannot be removed without breaking tons of code out there and the people making changes to the sparc64 cpus are painfully aware of this. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
