summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKévin Le Gouguec <kevin.legouguec@airbus.com>2019-07-05 11:06:43 +0200
committerKévin Le Gouguec <kevin.legouguec@airbus.com>2019-07-05 14:21:45 +0200
commitc242f47057cd3fdeb4471655b4cbd8c870fcf597 (patch)
tree7bd7b860ab8e60105e37c873d134b2d59842b21e
parent6539c825b51dcb1bf5181e5aba91cdc41ff0850f (diff)
downloadlilliput-ae-implem-c242f47057cd3fdeb4471655b4cbd8c870fcf597.tar.xz
Ajout d'une explication dans le changelog
-rw-r--r--CHANGELOG.txt19
1 files changed, 19 insertions, 0 deletions
diff --git a/CHANGELOG.txt b/CHANGELOG.txt
index 5a15c61..2e92008 100644
--- a/CHANGELOG.txt
+++ b/CHANGELOG.txt
@@ -38,6 +38,25 @@ ref
- lane 6: M_R^3 (unchanged)
(multiplications.h, tweakey.c)
+[break]
+- Make byte string concatenation more consistent in AE modes:
+
+ - v1 mixed two interpretations of concatenation:
+ 1. M_0 || M_1 was interpreted as { M[0], ... M[15] } || { M[16], ... M[31] },
+ 2. pad(10*) and tweak-building functions interpreted X||Y as { Y[0], ... Y[ylen-1] } || { X[0], ... X[xlen-1] }.
+
+ This was potentially confusing, and also led to inefficient hardware implementations. E.g. a message M of length 34 bytes was padded as follows:
+
+ M_0 M_1 pad10*(M_*)
+ { M[0], ... M[15] } || { M[16], ... M[31] } || { 0, ... 0, 0x80, M[32], M[33] }
+
+ - v1.1 sticks to the first interpretation. The same message M is now padded as follows:
+
+ M_0 M_1 pad10*(M_*)
+ { M[0], ... M[15] } || { M[16], ... M[31] } || { M[32], M[33], 0x80, 0, ... 0 }
+
+ (lilliput-ae-utils.h, lilliput-i.c, lilliput-ii.c)
+
add_felicsref
-------------