public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
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:52:20 +0200	[thread overview]
Message-ID: <CAKv+Gu9FE53zPhdUna-kiqvipBBrhi-sBG55SgXVGYAX_bQzXg@mail.gmail.com> (raw)
In-Reply-To: <a978c8e3-460d-12d4-a74f-2d44089ca562@redhat.com>

On 20 June 2017 at 17:44, Laszlo Ersek <lersek@redhat.com> wrote:
> On 06/20/17 14:00, Leif Lindholm wrote:
>> On Tue, Jun 20, 2017 at 01:28:38PM +0200, Ard Biesheuvel wrote:
>>> (+ Laszlo)
>>>
>>> On 20 June 2017 at 13:00, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>>>> When building without LTO, gcc incorrectly resolves the hazards for
>>>> 'PciRegBase’ when inlining, leading to "may be used uninitialized"
>>>> warnings (and hence build failure with -Werror).
>>>> Eliminate this warning by explicitly initializing the variable to 0.
>>>>
>>>> Contributed-under: TianoCore Contribution Agreement 1.0
>>>> Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org>
>>>
>>> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>
>> Thanks!
>>
>>>> ---
>>>>
>>>> For those who have heard me mentioning this before but arguing against
>>>> upstreaming this patch: I only just tweaked that this warning doesn't
>>>> go away with more recent toolchains, but simply when switching to GCC5
>>>> build profile, and hence LTO. Build failure still reproducible with
>>>> gcc 6.3.1 and GCC49.
>>>
>>> /me annoyed
>>
>> +1
>>
>>> We keep hitting this with GCC, and I profoundly dislike having to add
>>> redundant initialization sequences. Is there any other solution
>>> possible, e.g., disable this warning for certain builds?
>>
>> I would really like to not disable it.
>> When it gets it right, that's usually a pretty horrific bug caught.
>> And if we switch to LTO as the norm, I guess these will become less
>> noticeable over time.
>> But it does bug me too.
>
> 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


  reply	other threads:[~2017-06-20 19:50 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 [this message]
2017-06-20 19:57         ` Laszlo Ersek
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=CAKv+Gu9FE53zPhdUna-kiqvipBBrhi-sBG55SgXVGYAX_bQzXg@mail.gmail.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