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] benchtest: Link bench-malloc-thread with libm
Date: Fri,  3 Jun 2022 14:12:16 +0000 (GMT)	[thread overview]
Message-ID: <20220603141216.C7CE23856DF7@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=04a7d3c6bac8ee2772184b9c9ef457c640bdc77d

commit 04a7d3c6bac8ee2772184b9c9ef457c640bdc77d
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Mon Apr 4 09:33:07 2022 -0300

    benchtest: Link bench-malloc-thread with libm
    
    It uses powf and compiler might not optimize it away.

Diff:
---
 benchtests/Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/benchtests/Makefile b/benchtests/Makefile
index d6cd9e661c..f1a8795f08 100644
--- a/benchtests/Makefile
+++ b/benchtests/Makefile
@@ -285,6 +285,7 @@ $(addprefix $(objpfx)bench-,$(bench-pthread)): $(thread-library-benchtests)
 $(addprefix $(objpfx)bench-,$(bench-malloc)): $(thread-library-benchtests)
 $(addprefix $(objpfx)bench-,pthread-locks): $(libm-benchtests)
 $(addprefix $(objpfx)bench-,pthread-mutex-locks): $(libm-benchtests)
+$(addprefix $(objpfx)bench-,malloc-thread): $(libm-benchtests)


             reply	other threads:[~2022-06-03 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 14:12 Adhemerval Zanella [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-09 21:26 Adhemerval Zanella
2022-06-09 13:22 Adhemerval Zanella
2022-05-13 14:26 Adhemerval Zanella
2022-05-12 19:39 Adhemerval Zanella
2022-05-10 18:30 Adhemerval Zanella
2022-04-29 14:10 Adhemerval Zanella
2022-04-04 13:01 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=20220603141216.C7CE23856DF7@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: 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).