diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2017-11-10 15:33:28 -0500 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2017-11-10 15:33:30 -0500 |
| commit | 61fb80660f73e5aa5b69302ecc7ac33da206ba5a (patch) | |
| tree | 1b7b5b18cb3b7f989de87847ddaeb49e24f4fa29 /doc/release-notes | |
| parent | 05a761932edd05cf94ffe938908baf058f38632a (diff) | |
| parent | 203a4aa31eee402755f7156593228ab55407cc47 (diff) | |
| download | bitcoin-61fb80660f73e5aa5b69302ecc7ac33da206ba5a.tar.xz | |
Merge #11269: [Mempool] CTxMemPoolEntry::UpdateAncestorState: modifySiagOps param type
203a4aa31 Fix CTxMemPoolEntry::UpdateAncestorState: modifySigOps param type int -> int64_t (donaloconnor)
Pull request description:
CTxMemPoolEntry::CTxMemPoolEntry's modifySigOps parameter is int while update_ancestor_state::modifySigOpsCost is int64_t. This issue was raised in #11165. It looks like the function paramaters were not changed in commit 72abd2c
This will avoid unexpected truncation of int64_t -> int
Tree-SHA512: 314c703f217e104336456859066d18fb0d12c4f9f32835e17490a6f29eb05951184095039e4e57edacef8ad35dd75c6d97d9af656a52209dd0c3779b4ffa0914
Diffstat (limited to 'doc/release-notes')
0 files changed, 0 insertions, 0 deletions