Fwd: Re: gcc -> clang

[Rupert Gallagher]

Same problem with 2.3.4.

configure lacks debug flags.

No joy with gdb breakpoint in mallock_error_break on make test.

On Thu, Jan 3, 2019 at 13:58, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:

> The arithmetic stuff has already been fixed in master with
>
> https://github.com/dovecot/core/commit
> /5cccb4af850bb3ba81e73a8fb4f6881c3e1d4046.patch
> https://github.com/dovecot/core/commit
> /ac7aa955db4c77bbb169baa5d104a4c128674646.patch
>
> I have not seen the second error ever, it would need more information, can you gdb to it and see what the actual value is?
>
> Aki
>
>> On 03 January 2019 at 13:38 Rupert Gallagher via dovecot <dovecot at dovecot.org> wrote:
>>
>>
>> The compiler returns many warnings, and the test returns two IPv6-related errors. I am attaching both logs as reference.
>>
>> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> > On Thursday, January 3, 2019 9:53 AM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>> >
>> >> We compile all core code with both gcc and clang. What sort of interesting things did you find?
>> >>
>> >> Aki
>> >>
>> >>> On 03 January 2019 at 11:50 Rupert Gallagher via dovecot < dovecot at dovecot.org> wrote:
>> >>>
>> >>> 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.
>> >>
>> >> ---
>> >> Aki Tuomi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20190105/7353cf96/attachment.html>