public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Ryan Harkin <ryan.harkin@linaro.org>
Subject: Re: [PATCH] ArmPlatformPkg: eliminate Juno gcc build warning
Date: Tue, 20 Jun 2017 21:57:28 +0200	[thread overview]
Message-ID: <7b100a93-eafc-651a-515d-6cc329a99a35@redhat.com> (raw)
In-Reply-To: <CAKv+Gu9FE53zPhdUna-kiqvipBBrhi-sBG55SgXVGYAX_bQzXg@mail.gmail.com>

On 06/20/17 21:52, Ard Biesheuvel wrote:
> On 20 June 2017 at 17:44, Laszlo Ersek <lersek@redhat.com> wrote:

>> Perhaps we should introduce two macros to "MdePkg/Include/Base.h",
>>
>> #define UNUSED_POINTER NULL
>> #define UNUSED_INTEGER 0
>>
>> These could be used to suppress such warnings, without the risk of
>> misleading programmers (as to the real necessity of the variable
>> assignment at hand).
>>
> 
> Or perhaps
> 
> #ifdef __GNUC__
> #define USED(var)  var = (typeof(var))0
> #else
> #define USED(var)
> #endif
> 

Sure, why not :)


  reply	other threads:[~2017-06-20 19:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 11:00 [PATCH] ArmPlatformPkg: eliminate Juno gcc build warning Leif Lindholm
2017-06-20 11:28 ` Ard Biesheuvel
2017-06-20 11:44   ` Ryan Harkin
2017-06-20 12:04     ` Leif Lindholm
2017-06-20 12:00   ` Leif Lindholm
2017-06-20 15:44     ` Laszlo Ersek
2017-06-20 19:52       ` Ard Biesheuvel
2017-06-20 19:57         ` Laszlo Ersek [this message]
2017-06-20 20:05         ` Leif Lindholm

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-list 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=7b100a93-eafc-651a-515d-6cc329a99a35@redhat.com \
    --to=devel@edk2.groups.io \
    /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