From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: Fix memleak in getdelim.m4
Date: Fri, 22 May 2020 16:03:06 +0200 [thread overview]
Message-ID: <fb21c1af-f68b-0fb3-5f00-b87adc1f7c10@gmx.de> (raw)
In-Reply-To: <1600037.TtxsOjzTvg@omega>
[-- Attachment #1.1: Type: text/plain, Size: 778 bytes --]
Hi Bruno,
On 21.05.20 21:31, Bruno Haible wrote:
> Hi Tim,
>
> These comparisons are not so useful, because they not only come from different
> compilers (gcc vs. clang) but also from systems with different libcs: there
> are differences regarding libm, calloc, thrd_create, pthread_sigmask, and other
> functions. It would be more useful to compare, on the _same_ system:
> - gcc vs. clang,
> - clag vs. clang -fsanitize=...
Well, all made on the _same_ system (my desktop) with just ~35 minutes
in between.
Since system updates are made manually, it is _very_ unlikely that I
made an update between the tests.
But yes, I made one test without $CC set (so likely with gcc) and the
other one with CC=clang and CFLAGS=-fsanitize...
Regards, Tim
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-22 14:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 10:43 Fix memleak in getdelim.m4 Tim Rühsen
2020-05-18 11:50 ` Bruno Haible
2020-05-18 18:21 ` Tim Rühsen
2020-05-18 19:44 ` Bruno Haible
2020-05-19 21:47 ` Tim Rühsen
2020-05-19 22:46 ` Bruno Haible
2020-05-20 18:45 ` Tim Rühsen
2020-05-21 14:22 ` relicense module 'group-member' Bruno Haible
2020-05-21 14:44 ` Eric Blake
2020-05-21 15:10 ` Jim Meyering
2020-05-21 19:46 ` Bruno Haible
2020-05-21 19:27 ` Paul Eggert
2020-05-21 14:23 ` Fix memleak in getdelim.m4 Bruno Haible
2020-05-20 21:59 ` Tim Rühsen
2020-05-21 14:26 ` Bruno Haible
2020-05-21 16:11 ` Tim Rühsen
2020-05-21 19:31 ` Bruno Haible
2020-05-22 14:03 ` Tim Rühsen [this message]
2020-05-22 15:25 ` Bruno Haible
2020-05-22 20:46 ` Tim Rühsen
2020-05-23 17:51 ` Fix exponentl.m4 test Bruno Haible
2020-05-23 18:48 ` Fix calloc.m4 test Bruno Haible
2020-05-23 20:26 ` Paul Eggert
2020-05-23 21:53 ` Bruno Haible
2020-05-24 0:51 ` Paul Eggert
2020-05-24 7:53 ` Bruno Haible
2020-06-06 8:19 ` Bruno Haible
2020-05-23 19:18 ` Fix invalid use of __builtin_isnanf and __builtin_isnanl Bruno Haible
2020-05-23 20:18 ` Fix calloc-gnu configure results Bruno Haible
2020-05-23 20:47 ` Fix memleak in getdelim.m4 Bruno Haible
2020-05-24 8:39 ` Tim Rühsen
2020-05-21 15:15 ` SA_RESETHAND Bruno Haible
2020-05-21 20:10 ` SA_RESETHAND Paul Eggert
2020-05-21 20:59 ` SA_RESETHAND Bruno Haible
2020-05-21 15:22 ` Fix sanitizer error in fchownat.m4 Bruno Haible
2020-05-21 17:42 ` Fix memleak in glob.m4 Bruno Haible
2020-05-21 18:31 ` Fix memleak in regex.m4 Bruno Haible
2020-05-21 18:40 ` Fix memleak in getdelim.m4 Bruno Haible
2020-05-21 19:30 ` Paul Eggert
2020-05-21 19:38 ` Bruno Haible
2020-05-21 14:32 ` Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb21c1af-f68b-0fb3-5f00-b87adc1f7c10@gmx.de \
--to=tim.ruehsen@gmx.de \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).