From: Kirill Yukhin <kyukhin@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Georgy Kirichenko <georgy@tarantool.org>,
Alexander Turenko <alexander.turenko@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 0/3] Add LTO support
Date: Thu, 25 Oct 2018 15:18:54 +0300 [thread overview]
Message-ID: <20181025121854.ef3bjm5xkm4f3bo5@tarantool.org> (raw)
In-Reply-To: <cover.1539556251.git.alexander.turenko@tarantool.org>
Hello,
On 15 Oct 02:17, Alexander Turenko wrote:
> Changes since the last Alex's patch:
>
> * Discarded submodules update in order to use
> `set(CMAKE_POLICY_DEFAULT_CMP0069 NEW)` (deleted the branches).
> * Splitted ld / gold version parsing.
> * Always give an error when LTO is requested, but cannot be enabled for
> some reason.
> * Added more comments to cmake/lto.cmake.
> * Suppressed -Wlto-type-mismatch wargings, filed #3742.
> * Noted that LuaJIT will not be subject for LTO, filed #3743.
> * Rebased on top of fresh 1.10, rewrote CI targets definitions.
>
> https://github.com/tarantool/tarantool/issues/3117
> https://github.com/tarantool/tarantool/tree/kh/gh-3117-lto-3
> https://travis-ci.org/tarantool/tarantool/builds/441418628
I've checked the patchset into 2.1 branch.
--
Regards, Kirill Yukhin
prev parent reply other threads:[~2018-10-25 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 23:17 [tarantool-patches] " Alexander Turenko
2018-10-14 23:17 ` [tarantool-patches] [PATCH v2 1/3] test: prevent guard-breaker optimization with LTO Alexander Turenko
2018-10-14 23:17 ` [tarantool-patches] [PATCH v2 2/3] Add LTO support Alexander Turenko
2018-10-16 18:09 ` [tarantool-patches] " Konstantin Osipov
2018-10-17 7:13 ` Alexander Turenko
2018-10-25 11:17 ` Georgy Kirichenko
2018-10-14 23:17 ` [tarantool-patches] [PATCH v2 3/3] test: add LTO targets into CI Alexander Turenko
2018-10-25 11:16 ` [tarantool-patches] " Georgy Kirichenko
2018-10-25 12:18 ` Kirill Yukhin [this message]
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=20181025121854.ef3bjm5xkm4f3bo5@tarantool.org \
--to=kyukhin@tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=georgy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v2 0/3] Add LTO support' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox