aboutsummaryrefslogtreecommitdiffstats
path: root/docs/bugs.json
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2018-09-04 22:55:45 +0800
committerchriseth <chris@ethereum.org>2018-09-10 18:47:46 +0800
commitb84a1b390b2a5cc495b32e8757cac7efde294cc9 (patch)
tree366c89a5c54405a352946e6a297bfa09ff429229 /docs/bugs.json
parent120438c0cf7abc506ca90221bafa2a9cbbb12994 (diff)
downloaddexon-solidity-b84a1b390b2a5cc495b32e8757cac7efde294cc9.tar.gz
dexon-solidity-b84a1b390b2a5cc495b32e8757cac7efde294cc9.tar.zst
dexon-solidity-b84a1b390b2a5cc495b32e8757cac7efde294cc9.zip
Changelog entry and bug list.
Diffstat (limited to 'docs/bugs.json')
-rw-r--r--docs/bugs.json7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/bugs.json b/docs/bugs.json
index cf03adfe..b629d485 100644
--- a/docs/bugs.json
+++ b/docs/bugs.json
@@ -1,5 +1,12 @@
[
{
+ "name": "ExpCleanupZero",
+ "summary": "Using exponentiating with types shorter than 256 bits and zero as base can result in unexpected values.",
+ "description": "As defined by the EVM, 0 ** 0 is one. Solidity does not always remove dirty higher order bits of types that are smaller than 256 bits before applying an operation because it does not matter if the cleanup is performed before or after the operation. This is true for EXP except for the case where the base is zero, which was overlooked.",
+ "fixed": "0.5.0",
+ "severity": "high"
+ },
+ {
"name": "EventStructWrongData",
"summary": "Using structs in events logged wrong data.",
"description": "If a struct is used in an event, the address of the struct is logged instead of the actual data.",