From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdazzle/
Date: Sun, 28 Jul 2019 20:22:52 +0000 (UTC) [thread overview]
Message-ID: <1564345355.5ca71b7a2ee06d6549e8e4ff537e031445c63f8c.leio@gentoo> (raw)
commit: 5ca71b7a2ee06d6549e8e4ff537e031445c63f8c
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 28 20:19:23 2019 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sun Jul 28 20:22:35 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5ca71b7a
dev-libs/libdazzle: explicitly disable rdtscp and add reason comments
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>
dev-libs/libdazzle/libdazzle-3.32.3.ebuild | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/dev-libs/libdazzle/libdazzle-3.32.3.ebuild b/dev-libs/libdazzle/libdazzle-3.32.3.ebuild
index ac1010df863..22a3edefeeb 100644
--- a/dev-libs/libdazzle/libdazzle-3.32.3.ebuild
+++ b/dev-libs/libdazzle/libdazzle-3.32.3.ebuild
@@ -41,7 +41,10 @@ src_configure() {
local emesonargs=(
-Denable_tracing=false # extra trace debugging that would make things slower
-Denable_profiling=false # -pg passing
- # -Denable_rdtscp=false # TODO: CPU_FLAGS_X86 for it?
+ # On linux it'll always use a vdso based implementation that is even faster
+ # than rdtscp insn, thus never build with rdtscp until we don't support non-linux
+ # as the rdtscp using function will never get called anyways.
+ -Denable_rdtscp=false
-Denable_tools=true # /usr/bin/dazzle-list-counters
$(meson_use introspection with_introspection)
$(meson_use vala with_vapi)
next reply other threads:[~2019-07-28 20:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 20:22 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-24 10:46 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdazzle/ WANG Xuerui
2022-10-29 23:21 Matt Turner
2022-03-22 2:46 Matt Turner
2021-12-18 23:39 Matt Turner
2021-09-28 14:53 Yixun Lan
2021-04-12 21:59 Matt Turner
2021-04-12 21:59 Matt Turner
2020-12-08 11:46 Mart Raudsepp
2020-07-17 10:20 Mart Raudsepp
2020-03-01 16:18 Mart Raudsepp
2019-12-23 21:26 Mart Raudsepp
2019-10-27 12:16 Mart Raudsepp
2019-08-05 0:34 Aaron Bauman
2019-07-27 6:49 Mart Raudsepp
2019-01-14 19:52 Mart Raudsepp
2019-01-14 14:39 Mikle Kolyada
2019-01-09 1:39 Thomas Deutschmann
2018-12-19 22:31 Sergei Trofimovich
2018-12-19 22:31 Sergei Trofimovich
2018-12-02 13:34 Mikle Kolyada
2018-10-09 21:14 Sergei Trofimovich
2018-09-12 14:39 Thomas Deutschmann
2018-08-29 21:57 Mart Raudsepp
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=1564345355.5ca71b7a2ee06d6549e8e4ff537e031445c63f8c.leio@gentoo \
--to=leio@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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