bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fix memleak in getdelim.m4


From: Tim Rühsen
Subject: Re: Fix memleak in getdelim.m4
Date: Fri, 22 May 2020 22:46:54 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0

Hi Bruno,

On 22.05.20 17:25, Bruno Haible wrote:
>> But yes, I made one test without $CC set (so likely with gcc) and the
>> other one with CC=clang and CFLAGS=-fsanitize...
> 
> Then it would be useful to have the config.{cache,log,status} results also
> for a build where CC=clang but CFLAGS unset. So as to distinguish which
> differences come from clang vs. gcc and which come from the sanitizers.
> 
> Each of these differences points to a possible problem in our *.m4 macros.

Attached is the config.log and config.cache for
- gcc-9 with unset CFLAGS (*.gcc-9)
- clang-9 with unset CFLAGS (*.clang-9)
- gcc-10 with unset CFLAGS (*.gcc-10)
- clang-10 with unset CFLAGS (*.clang-10)

And the same set with -fsanitize... (*.sanitize).

The sanitizer flags for gcc and clang differ in that clang supports
"integer" and "nullability" while gcc does not.

You find the exact flags in config.log.*.sanitize files.

The gnulib commit was 9bf6b3cafa2a39c09143182f2271d6c877eabfdc (latest
master from this evening).

Regards, Tim

Attachment: config.tar.lz
Description: Binary data

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]