tersec

Unintentional, triggered by https://github.com/status-im/nimbus-eth2/pull/6292

Fixed by https://github.com/status-im/nimbus-eth2/commit/68eabc098b6ff5a3dd9033c6c5f24743a5731096

The specific error currently appears to be the Linux max stack checking: ``` gcc @nimcache/release/all_tests/all_tests.makefile.linkerArgs /github-runner/workspace/nimbus-eth2/nimbus-eth2/vendor/nim-chronos/chronos/internal/asyncmacro.nim: In function ‘_ZN16readChunkPayload61readChunkPayload__OOZbeacon95chainZsyncZsync95protocol_u13995E3refIN7futures26FutureBasecolonObjectType_EE’: /github-runner/workspace/nimbus-eth2/nimbus-eth2/vendor/nim-chronos/chronos/internal/asyncmacro.nim:439:15: error: stack usage might be 1321040 bytes [-Werror=stack-usage=] 439 |...

> Of course its important because all this packages had `gcc-14` issues and all of them was fixed. Yes, everything in this PR is important, for that reason. But the...

They're distinct things, as the slightly broader context elucidates: https://github.com/status-im/nimbus-eth2/blob/d2a07514541ffe6ee02a2ec7272ce7a315131e04/config.nims#L68-L80 The 1MB limit comes from https://github.com/status-im/nimbus-eth2/pull/3055 which was a response to multi-MB maximum static stack sizes (https://github.com/status-im/nimbus-eth2/pull/3049) and sometimes resulting...

Is this PR still relevant?

Related issues: - https://github.com/status-im/nim-secp256k1/issues/56 - https://github.com/waku-org/nwaku/issues/2560 - https://github.com/status-im/nimbus-eth1/issues/2127

@tranphuocanh0207 if you run `gcc -march=native -Q --help=target` and look for `march`, `mcpu`, and `mtune` values, what does it show in your case? e.g. ``` $ gcc -march=native -Q --help=target...

That's strange, but, glad you were able to built it by specifying `-march=znver3` directly. It should work regardless, but this is a potential workaround until a root cause is discovered.

That stack trace looks like the symbol non-demangling one gets using Nim 2.0. What version of Nim is being used to compile this?