diff options
| author | fanquake <fanquake@gmail.com> | 2021-07-18 10:57:29 +0800 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2021-07-18 11:06:10 +0800 |
| commit | 6baabc4d1dfaf5a630c385e10e7d1fbb67c7b97d (patch) | |
| tree | edafb0b1a5352c33a34ba885ec97862b34e4b3c0 /test/functional/rpc_addresses_deprecation.py | |
| parent | f8b20fd35b0eb42d28afb302a070e5d9bc21a99f (diff) | |
| parent | 3c4c8e79baf02af97ba1502189f649b04ef2198d (diff) | |
| download | bitcoin-6baabc4d1dfaf5a630c385e10e7d1fbb67c7b97d.tar.xz | |
Merge bitcoin/bitcoin#21430: build: Add -Werror=implicit-fallthrough compile flag
3c4c8e79baf02af97ba1502189f649b04ef2198d build: Add -Werror=implicit-fallthrough compile flag (Hennadii Stepanov)
014110c47d94ece6e3e655cdbf02ed8c91c7a5cf Use C++17 [[fallthrough]] attribute, and drop -Wno-implicit-fallthrough (Hennadii Stepanov)
Pull request description:
ACKs for top commit:
fanquake:
ACK 3c4c8e79baf02af97ba1502189f649b04ef2198d - looks ok to me now. Checked that warnings occur in our code & leveldb by removing a `[[fallthrough]]` or `FALLTHROUGH_INTENDED`.
jarolrod:
ACK 3c4c8e79baf02af97ba1502189f649b04ef2198d
theStack:
ACK 3c4c8e79baf02af97ba1502189f649b04ef2198d
Tree-SHA512: 4dce91f0f26b8a3de09bd92bb3d7e1995e078e3a8b3ff861c4fbf6c0b32b2327d063633b07b89c4aa94a1141d7f78d46d9d43ab8df865273e342693ad30645b6
Diffstat (limited to 'test/functional/rpc_addresses_deprecation.py')
0 files changed, 0 insertions, 0 deletions