📝 fanquake converted_to_draft a pull request: "guix: use GCC 12.3.0 to build releases"
(https://github.com/bitcoin/bitcoin/pull/27897)
Switch to using [GCC `12.3.0`](https://gcc.gnu.org/gcc-12/) to build release binaries.

Update the vmov-alignment patch, for changes in GCC 12.

Guix Build:
```bash
TBD
```

✅ achow101 closed a pull request: "datacarriersize: Match more datacarrying"
(https://github.com/bitcoin/bitcoin/pull/28408)

💬 achow101 commented on pull request "datacarriersize: Match more datacarrying":
(https://github.com/bitcoin/bitcoin/pull/28408#issuecomment-1878853896)
It's abundantly clear that this PR is controversial and, in its current state, has no hope of reaching a conclusion that is acceptable to everyone. At this point in time, I see no reason to leave this open and to continue to send notifications for the constant back-and-forth stalemate discussion.

📝 achow101 locked a pull request: "datacarriersize: Match more datacarrying"
(https://github.com/bitcoin/bitcoin/pull/28408)
Updates `-datacarriersize` to be effective with newer datacarrying styles.

💬 hebasto commented on pull request "build: remove `--enable-lto`":
(https://github.com/bitcoin/bitcoin/pull/29185#issuecomment-1878858797)
Concept ACK.

💬 fanquake commented on pull request "build: remove `--enable-lto`":
(https://github.com/bitcoin/bitcoin/pull/29185#issuecomment-1878861715)
> Can you explain what that means? Is the recommended way to manually override CXXFLAGS and LDFLAGS now?

Yea. `-flto` is really no different to `-O2` or any other compile option, so using it will require adding `-flto=*`, and any other related options you might want, i.e using a link cache via `-Wl,-cache_path_lto`, to the respective *FLAGS vars. Note that this is already required by anyone wanting to do anything other, or in addion to just using `-flto` with the current options (or they'd ha
...

👍 hebasto approved a pull request: "crypto: remove use of BUILD_BITCOIN_INTERNAL macro in sha256"
(https://github.com/bitcoin/bitcoin/pull/29180#pullrequestreview-1806188076)
ACK 86712c3135786b305f27c44dffd0808be0ee7170.

💬 hebasto commented on pull request "crypto: remove use of BUILD_BITCOIN_INTERNAL macro in sha256":
(https://github.com/bitcoin/bitcoin/pull/29180#discussion_r1443020894)
typo: unoptomized --> unoptimized

🚀 fanquake merged a pull request: "doc: Clarify C++20 comments"
(https://github.com/bitcoin/bitcoin/pull/29042)

🚀 fanquake merged a pull request: "build: remove systemtap variadic patch"
(https://github.com/bitcoin/bitcoin/pull/29181)

💬 maflcko commented on pull request "build: remove `--enable-lto`":
(https://github.com/bitcoin/bitcoin/pull/29185#issuecomment-1878872129)
> to the respective *FLAGS vars

Ah, I guess this would disable O2, see https://github.com/bitcoin/bitcoin/pull/28071/files. So I guess it would have to be appended to `CXX` and possibly `LDFLAGS`.

💬 brunoerg commented on pull request "fuzz: set `nMaxOutboundLimit` in connman target":
(https://github.com/bitcoin/bitcoin/pull/29172#discussion_r1443029230)
I agree, just addressed it.

💬 jamesob commented on pull request "doc: Add multiprocess design doc":
(https://github.com/bitcoin/bitcoin/pull/28978#issuecomment-1878878185)
Post-merge ACK. This doc is very helpful, thanks @ryanofsky!

💬 brunoerg commented on pull request "fuzz: set `nMaxOutboundLimit` in connman target":
(https://github.com/bitcoin/bitcoin/pull/29172#discussion_r1443035779)
The idea was to have more runs with the default value, but just tested here and in practice it didn't have so much effect. Just changed it to your suggestion.

💬 brunoerg commented on pull request "fuzz: set `nMaxOutboundLimit` in connman target":
(https://github.com/bitcoin/bitcoin/pull/29172#issuecomment-1878883840)
Thanks, @dergoegge for your review. Force-pushed addressing: https://github.com/bitcoin/bitcoin/pull/29172#discussion_r1442764742 and https://github.com/bitcoin/bitcoin/pull/29172#discussion_r1442763249.

📝 hebasto opened a pull request: "ci, iwyu: Drop backported mappings"
(https://github.com/bitcoin/bitcoin/pull/29186)
See https://github.com/include-what-you-use/include-what-you-use/pull/1026.

Split from https://github.com/bitcoin/bitcoin/pull/27710 as a non-controversial change.

💬 maflcko commented on pull request "build: LLD based macOS toolchain":
(https://github.com/bitcoin/bitcoin/pull/21778#issuecomment-1878901826)
> * Building for mac, on Linux, using our downloaded LLVM (Clang + lld + tools)
>
> * Building for mac, in Guix, using Guix's Clang + our downloaded lld + tools??
>
> * Or shift further into using all Guix linker + tools, or, try drop Guix Clang?

I think the benefit of using guix (over downloading a random binary blob from someone else's computer) is that cross compilation to macOS works on more architectures than the uploads of the llvm binaries. (For example riscv64)

So simply
...

💬 fanquake commented on pull request "build: LLD based macOS toolchain":
(https://github.com/bitcoin/bitcoin/pull/21778#issuecomment-1878913852)
> and nuking clang from depends,

After discussion today with @theuni @hebasto @TheCharlatan, I'm actually about to open a PR to do exactly this.

💬 mzumsande commented on pull request "net, cli: use v2transport for manual/addrfetch connections, add to -netinfo":
(https://github.com/bitcoin/bitcoin/pull/29058#issuecomment-1878918062)
> an interesting behaviour which i realised made sense was to keep retrying with v2 when latency issue failures happen on tor.

Yes! The connection must have been established on the TCP/IP level for a reconnection attempt to happen. It's the same reason why we don't try to reconnect with v1 if the peer is just offline.

💬 fjahr commented on pull request "refactor: C++20: Use std::rotl":
(https://github.com/bitcoin/bitcoin/pull/29085#issuecomment-1878920263)
> Any reason not to do `Rotl` in sha3 and `ROTL` in siphash as well?

I don't see any, apparently I just need to learn to grep patterns better...