aboutsummaryrefslogtreecommitdiffstats
path: root/docs/bugs.json
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2017-04-18 17:40:00 +0800
committerchriseth <chris@ethereum.org>2017-04-18 17:40:00 +0800
commit11d30ec04fcc7d017fe3c419c6ad64f657a17e96 (patch)
tree42657ac09468d4c09c0eb67a856ad7f23fd8ad83 /docs/bugs.json
parent10c32362ead6b5198221a48605e16c89a7800deb (diff)
downloaddexon-solidity-11d30ec04fcc7d017fe3c419c6ad64f657a17e96.tar.gz
dexon-solidity-11d30ec04fcc7d017fe3c419c6ad64f657a17e96.tar.zst
dexon-solidity-11d30ec04fcc7d017fe3c419c6ad64f657a17e96.zip
Some changes after review.
Diffstat (limited to 'docs/bugs.json')
-rw-r--r--docs/bugs.json2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/bugs.json b/docs/bugs.json
index 4e7f1245..2a8d167a 100644
--- a/docs/bugs.json
+++ b/docs/bugs.json
@@ -30,7 +30,7 @@
"name": "OptimizerStaleKnowledgeAboutSHA3",
"summary": "The optimizer did not properly reset its knowledge about SHA3 operations resulting in some hashes (also used for storage variable positions) not being calculated correctly.",
"description": "The optimizer performs symbolic execution in order to save re-evaluating expressions whose value is already known. This knowledge was not properly reset across control flow paths and thus the optimizer sometimes thought that the result of a SHA3 operation is already present on the stack. This could result in data corruption by accessing the wrong storage slot.",
- "severity": "low/medium",
+ "severity": "medium",
"fixed": "0.4.3",
"conditions": {
"optimizer": true