diff options
| author | merge-script <fanquake@gmail.com> | 2024-09-17 09:47:44 +0100 |
|---|---|---|
| committer | merge-script <fanquake@gmail.com> | 2024-09-17 09:47:44 +0100 |
| commit | 225718eda89d65a7041c33e1994d3bf7bd71bbdd (patch) | |
| tree | eb869933eb84015d3e05299533351f8d79e384de /test/functional/wallet_spend_unconfirmed.py | |
| parent | 9f1aa88d4d9596aeb5220fa30ee3972294b62793 (diff) | |
| parent | 89bf11b807252fe5839b5b18742e24568dfe7bbd (diff) | |
Merge bitcoin/bitcoin#30438: guix: (explicitly) build Linux GCC with `--enable-cet`
89bf11b807252fe5839b5b18742e24568dfe7bbd guix: build Linux GCC with --enable-cet (fanquake)
Pull request description:
Similar to #29695, and in the same vein of explicitly configuring hardening options in our release toolchain.
See https://gcc.gnu.org/install/configure.html:
>` --enable-cet`
> Enable building target run-time libraries with control-flow instrumentation, see `-fcf-protection option`. When --enable-cet is specified target libraries are configured to add `-fcf-protection` and, if needed, other target specific options to a set of building options.
> `--enable-cet=auto` is default. CET is enabled on Linux/x86 if target binutils supports Intel CET instructions and disabled otherwise. In this case, the target libraries are configured to get additional `-fcf-protection` option.
ACKs for top commit:
TheCharlatan:
ACK 89bf11b807252fe5839b5b18742e24568dfe7bbd
Tree-SHA512: 772d8529713a31e5db42be4e053582bb9ba6f26079ae136c6bf8303c4992a90d61159dbb0fde7a4b4cb7b4bf5024d5397a78004e6188b36e1c36dd5e5cdc49ad
Diffstat (limited to 'test/functional/wallet_spend_unconfirmed.py')
0 files changed, 0 insertions, 0 deletions