Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@freelists.org,
	Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] Fix Debug build on GCC 8
Date: Thu, 20 Sep 2018 18:42:47 +0300	[thread overview]
Message-ID: <20180920154247.vqm6m3a5bwofyeyx@tarantool.org> (raw)
In-Reply-To: <8c538963a78f22746233b22648fb2aa6933dc135.1536991382.git.alexander.turenko@tarantool.org>

Hello,
On 15 сен 09:07, Alexander Turenko wrote:
> Fixed false positive -Wimplicit-fallthrough in http_parser.c by adding a
> break. The code jumps anyway, so the execution flow is not changed.
> 
> Fixed false positive -Wparenthesis in reflection.h by removing the
> parentheses. The argument 'method' of the macro 'type_foreach_method' is
> just name of the loop variable and is passed to the macro for
> readability reasons.
> 
> Fixed false positive -Wcast-function-type triggered by reflection.h by
> adding -Wno-cast-function-type for sources and unit tests. We cast a
> pointer to a member function to an another pointer to member function to
> store it in a structure, but we cast it back before made a call. It is
> legal and does not lead to an undefined behaviour.
> 
> Fixes #3685.
> ---
> 
> issue: https://github.com/tarantool/tarantool/issues/3685
> branch: https://github.com/tarantool/tarantool/tree/Totktonada/gh-3685-fix-debug-build-gcc-8
> travis-ci: https://travis-ci.org/tarantool/tarantool/builds/428903995
I've checked the patch into 1.9 branch.

--
Regards, Kirill Yukhin

      reply	other threads:[~2018-09-20 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15  6:07 [tarantool-patches] " Alexander Turenko
2018-09-20 15:42 ` 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=20180920154247.vqm6m3a5bwofyeyx@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH] Fix Debug build on GCC 8' \
    /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