start filling in

[libreriscv.git] / isa_conflict_resolution.mdwn

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index 6de6852cc3d79a9e0b75652ba9eab6df8e5e741e..bf036f64907955bde74e7b1eee0b7823d5a247ee 100644 (file)
--- a/isa_conflict_resolution.mdwn
+++ b/isa_conflict_resolution.mdwn
@@ -224,7 +224,7 @@ take into account the flaws pointed out by trying to use "MISA":
 Whilst it was the first "workable" solution it was also noted that the
 scheme is invasive: it requires an entirely new CSR to be added
 to the privileged spec (thus making existing implementations redundant).
-This does not completely fulfil the "minimum impact" requirement.
+This does not fulfil the "minimum impact" requirement.
 
 Also interesting around the same time an additional discussion was
 raised that covered the *compiler* side of the same equation.  This
@@ -239,13 +239,13 @@ separate page?  review this para?**)
 
 TBD paraphrase and clarify
 
-Coming out of the software-related proposal by Jacob, which hinged on
-the idea of a global gcc / binutils database that kept and coordinated
-architectural encodings, was to quite simply make the mvendorid and
-marchid CSRs have WARL (writeable) characteristics.  For instances
-where mvendorid and marchid are readable, that would be taken to be
-a Standards-mandatory "declaration" that the architecture has *no*
-Custom Extensions.
+Coming out of the software-related proposal by Jacob Bachmeyer, which
+hinged on the idea of a globally-maintained gcc / binutils database
+that kept and coordinated architectural encodings (curated by the Free
+Software Foundation), was to quite simply make the mvendorid and marchid
+CSRs have WARL (writeable) characteristics.  For instances where mvendorid
+and marchid are readable, that would be taken to be a Standards-mandatory
+"declaration" that the architecture has *no* Custom Extensions.
 
 This incredibly simple non-invasive idea has some unique and distinct
 advantages over other proposals: