Open anatol opened 2 months ago
Hmm, we do take the address of a local there, but it is safe as the call to walk()
will fully consume the data with that address. So this looks like a false positive.
But I'm not familiar with that error message so I'm not sure how best to work around it (or if there is a better solution than working around it).
I tried to google more about this problem. It looks like dangling-pointer
warnings were added recently and are prone to false positives. But I don't really know GCC/C++ well enough to debug the problem.
Another part of the issue is that the project enables -Werror
by default. Thus any warning (including false positive) becomes compilation error. tinygo
plans to disable it by -DENABLE_WERROR=OFF
.
Hi, here is a followup for https://github.com/tinygo-org/tinygo/issues/4332
I am trying to compile tinygo for Arch Linux in its clean build environment.
tinygo
in turn includebinaryen
(commit 11dba9b). Compilation forbinaryen
is invoked and it fails withMost likely the failure is related to one of the security fortfication flags used by Arch
CXXFLAGS="-O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wp,-D_GLIBCXX_ASSERTIONS -g"