<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">The unit test problems aren't clang issues, they're OSX issues. So:</div><div class=""><br class=""></div><div class=""><div class="">test-net.c:79: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0</div><div class="">test-net.c:83: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0</div></div><div class=""><br class=""></div><div class="">This is because OSX writes the address out as "::0.0.0.5" instead of "::5". I don't remember if the core code should be fixed or if it's just the unit test that needs fixing.</div><div class=""><br class=""></div><div class=""><div class="">test-lib(26058,0x7fff95cf7380) malloc: *** mach_vm_map(size=9223372036854775808) failed (error code=3)</div><div class="">*** error: can't allocate region</div><div class="">*** set a breakpoint in malloc_error_break to debug</div><div class="">fatal_mempool_alloconly .............................................. : ok</div><div class="">test-lib(26058,0x7fff95cf7380) malloc: *** mach_vm_map(size=9223372036854775808) failed (error code=3)</div><div class="">*** error: can't allocate region</div><div class="">*** set a breakpoint in malloc_error_break to debug</div></div><div class="">fatal_mempool_allocfree .............................................. : ok</div><div class=""><br class=""></div><div class="">I'm pretty sure these are intentional. The unit tests are succeeding, and the unit tests are there to test failing memory allocations. OSX just wants to also write some extra errors to stderr.</div><br class=""><div><blockquote type="cite" class=""><div class="">On 3 Jan 2019, at 13.38, Rupert Gallagher via dovecot <<a href="mailto:dovecot@dovecot.org" class="">dovecot@dovecot.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: UICTFontTextStyleBody; font-size: 17px;" class="">The compiler returns many warnings, and the test returns two IPv6-related errors. I am attaching both logs as reference. </span><br class=""></div><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: UICTFontTextStyleBody; font-size: 17px;" class=""><br class=""></span></div><blockquote class="protonmail_quote" type="cite"><div class="">‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br class=""></div><div class=""> On Thursday, January 3, 2019 9:53 AM, Aki Tuomi <<a href="mailto:aki.tuomi@open-xchange.com" class="">aki.tuomi@open-xchange.com</a>> wrote:<br class=""></div><div class=""> <br class=""></div><blockquote type="cite" class="protonmail_quote"><div class="">We compile all core code with both gcc and clang. What sort of interesting things did you find?<br class=""></div><div class=""><br class=""></div><div class="">Aki<br class=""></div><blockquote type="cite" class=""><div class="">On 03 January 2019 at 11:50 Rupert Gallagher via dovecot < <a href="mailto:dovecot@dovecot.org" class="">dovecot@dovecot.org</a>> wrote:<br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please, use clang instead of gcc. Code quality can only profit from it. I just compiled 2.3.4 and compiler stderr is full of interesting problems.<br class=""></div></blockquote><div class=""><br class=""></div><div class=""><div class="">--- <br class=""></div><div class="">Aki Tuomi</div></div></blockquote></blockquote><span id="cid:5BF12128-E1DC-4D80-B344-7E40890A0969@hsd1.fl.comcast.net"><compiler-stderr.log></span><span id="cid:AAF0D5A7-2623-43D1-9EAE-B5A989382A07@hsd1.fl.comcast.net"><test.log></span></div></blockquote></div><br class=""></body></html>