Niels, Thank you very much for the quick response.
> Also, Nettle's configure modifies CFLAGS (which is somewhat debatable), > so it may be more reliable with > > CC="clang -fsanitize=address" This indeed did the trick. It's still a bit mysterious why older versions of clang didn't have this problem, and just generally mysterious why the sanitizer would cause the issue. But, it does seem to be ok now (fwiw sanitizer does report a memory leak when eccdata is running at the end of make). On Tue, Apr 25, 2023 at 10:35 PM Niels Möller <ni...@lysator.liu.se> wrote: > > Noah Watkins <n...@redpanda.com> writes: > > > Hi nettle-bugs, > > > > We just updated to clang-16 and are encountering an issue compiling > > nettle with -fsanitize=address. > > > > Configured with > > > > CC=clang CXX=clang++ CFLAGS="-fsanitize=address" > > LDFLAGS="-fsanitize=address" ./configure --disable-documentation > > --enable-x86-aesni > > Note that --enable-x86-aesni has no effect in a fat build (which is the > default). If you really want to unconditionally use aesni instructions, you > need --disable-fat --enable-x86-aesni. Thanks a lot. I'm not entirely sure of the lineage of the flags we are using, but indeed the intention was to unconditionally enable so we'll apply this. > > To be clear, you mean the nettle-3.8.1 release? I was testing with a fresh clone of nettle from git as well as 3.8.1 release. - Noah _______________________________________________ nettle-bugs mailing list -- nettle-bugs@lists.lysator.liu.se To unsubscribe send an email to nettle-bugs-le...@lists.lysator.liu.se
