qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	SeokYeon Hwang <syeon.hwang@samsung.com>
Subject: Re: [Qemu-devel] [PATCH] translate-all: wrapped map_exec() in #ifdef
Date: Mon, 3 Nov 2014 15:05:53 +0000	[thread overview]
Message-ID: <CAFEAcA8Tov-2ewOdh9WVx3mp26M1yJjS7jV1D6s36huFsJQGAw@mail.gmail.com> (raw)
In-Reply-To: <545790EA.1080506@msgid.tls.msk.ru>

On 3 November 2014 14:27, Michael Tokarev <mjt@tls.msk.ru> wrote:

> I usually reluctant to add these unused attributes and shut up other
> warnings by force, because with time this cruft does not help, and
> more and more code becomes "forgotten".  If it is not needed for
> windows, why add it?

You could equally ask why we've marked the function "inline"
for both, when it's currently only required for non-win32
and only needed because it silences the warning on gcc.

> Hence the "untested" warning by me... So the test can be rewritten
> like this:
>
> #elif defined(USE_STATIC_CODE_GEN_BUFFER) || !defined(USE_MMAP)
>
> (untested again! ;) and everything should be well without adding
> extra attributes...  Which one is better is, well, a matter of
> personal taste really.. :)

Yeah, that's the "close coupling between warning-suppressing
and the implementation of a different bit of the code" approach.
As you say, personal taste; I've applied my r-by tag to the
other one ;-)

-- PMM

      reply	other threads:[~2014-11-03 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31  4:59 [Qemu-devel] [PATCH] translate-all: wrapped map_exec() in #ifdef SeokYeon Hwang
2014-10-31 18:30 ` Peter Maydell
2014-11-03  8:18   ` SeokYeon Hwang
2014-11-03  9:16     ` Michael Tokarev
2014-11-03 12:25       ` Peter Maydell
2014-11-03 14:27         ` Michael Tokarev
2014-11-03 15:05           ` Peter Maydell [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=CAFEAcA8Tov-2ewOdh9WVx3mp26M1yJjS7jV1D6s36huFsJQGAw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=syeon.hwang@samsung.com \
    /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 NNTP newsgroup(s).