public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/azanella/clang] malloc: Disable malloc builtins on tests Date: Thu, 28 Sep 2023 17:56:43 +0000 (GMT) [thread overview] Message-ID: <20230928175643.3EEC3382A2F2@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ca27004e1096ab2942dc770acccf835e52bc9d74 commit ca27004e1096ab2942dc770acccf835e52bc9d74 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Wed Mar 30 15:42:18 2022 -0300 malloc: Disable malloc builtins on tests To avoid compiler optimize away memory allocation calls, which might interfere when both valid and invalid calls checks. Diff: --- malloc/Makefile | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/malloc/Makefile b/malloc/Makefile index c1db3347d8..0e47b8446f 100644 --- a/malloc/Makefile +++ b/malloc/Makefile @@ -368,3 +368,18 @@ tst-mallocstate-malloc-check-ENV = LD_PRELOAD=$(objpfx)libc_malloc_debug.so # libc_malloc_debug.so. $(objpfx)tst-mallocstate: $(objpfx)libc_malloc_debug.so $(objpfx)tst-mallocstate-malloc-check: $(objpfx)libc_malloc_debug.so + +CFLAGS-tst-memalign.c += -fno-builtin +CFLAGS-tst-memalign-2.c += -fno-builtin +CFLAGS-tst-memalign-3.c += -fno-builtin +CFLAGS-tst-malloc.c += -fno-builtin +CFLAGS-tst-malloc-backtrace.c += -fno-builtin +CFLAGS-tst-malloc-check.c += -fno-builtin +CFLAGS-tst-malloc-too-large.c += -fno-builtin +CFLAGS-tst-realloc.c += -fno-builtin +CFLAGS-tst-valloc.c += -fno-builtin +CFLAGS-tst-compathooks-off.c += -fno-builtin +CFLAGS-tst-compathooks-on.c += -fno-builtin +CFLAGS-tst-mallinfo2.c += -fno-builtin +CFLAGS-tst-aligned-alloc.c += -fno-builtin +CFLAGS-tst-aligned-alloc-static.c += -fno-builtin
next reply other threads:[~2023-09-28 17:56 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-28 17:56 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-17 20:11 Adhemerval Zanella 2024-04-02 15:58 Adhemerval Zanella 2024-02-09 17:36 Adhemerval Zanella 2024-02-07 14:11 Adhemerval Zanella 2024-01-29 18:02 Adhemerval Zanella 2023-12-21 18:58 Adhemerval Zanella 2023-08-30 12:41 Adhemerval Zanella 2023-02-09 19:53 Adhemerval Zanella 2022-10-28 17:46 Adhemerval Zanella 2022-10-04 13:04 Adhemerval Zanella 2022-06-09 21:24 Adhemerval Zanella 2022-06-09 13:21 Adhemerval Zanella 2022-06-03 14:10 Adhemerval Zanella 2022-05-13 14:24 Adhemerval Zanella 2022-05-12 19:38 Adhemerval Zanella 2022-05-10 18:28 Adhemerval Zanella 2022-04-29 14:08 Adhemerval Zanella 2022-04-04 12:59 Adhemerval Zanella
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230928175643.3EEC3382A2F2@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@sourceware.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: linkBe 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).