From: Luke Kenneth Casson Leighton Date: Mon, 10 Apr 2023 10:21:44 +0000 (+0100) Subject: clarify purpose, add pagebreask to ls012 X-Git-Tag: opf_rfc_ls012_v1~34 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=05d0bda5d67d26b4733854c0a9264b3a85f4fb7c;p=libreriscv.git clarify purpose, add pagebreask to ls012 --- diff --git a/openpower/sv/rfc/ls012.mdwn b/openpower/sv/rfc/ls012.mdwn index 7b8fc548d..77df72492 100644 --- a/openpower/sv/rfc/ls012.mdwn +++ b/openpower/sv/rfc/ls012.mdwn @@ -9,8 +9,8 @@ The purpose of this RFC is: -* to give a full list of the upcoming Scalar opcodes developed by Libre-SOC - (respecting and being cognisant that *all* of them are Vectorisable) +* to give a full list of upcoming Scalar opcodes developed by Libre-SOC + (being cognisant that *all* of them are Vectorisable) * to give OPF Members and non-Members alike the opportunity to comment and get involved early in RFC submission * formally agree a priority order on an iterative basis with new versions @@ -19,9 +19,9 @@ The purpose of this RFC is: not proposed at all, * keep readers summarily informed of ongoing RFC submissions, with new versions of this RFC, -* and for IBM (in their capacity as Allocator of Opcode resources) - to get a clear overall advance picture of the Opcode Allocation needs - *prior* to actual RFC submission +* for IBM (in their capacity as Allocator of Opcodes) + to get a clear advance picture of Opcode Allocation + *prior* to submission As this is a Formal ISA RFC the evaluation shall ultimatly define (in advance of the actual submission of the instructions themselves) @@ -96,6 +96,8 @@ Summary tables are created below by different sort categories. Additional columns (and tables) as necessary can be requested to be added as part of update revisions to this RFC. +\newpage{} + # Target Area summaries Please note that there are some instructions developed thanks to NLnet @@ -385,6 +387,7 @@ Being a 10-bit XO it would be somewhat punitive to place these in EXT2xx when their whole purpose and value is to reduce binary size in Address offset computation, thus they are best placed in EXT0xx. +\newpage{} # Tables