From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Evan Lloyd <Evan.Lloyd@arm.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>, nd <nd@arm.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Stephanie Hughes-Fitt <Stephanie.Hughes-Fitt@arm.com>,
Matteo Carlini <Matteo.Carlini@arm.com>
Subject: Re: Query about variable initialization
Date: Wed, 20 Jun 2018 20:03:58 +0200 [thread overview]
Message-ID: <CAKv+Gu-KCEVTsnZKOY7roUecwVv6hAixgvjZivSi0u0HAMUpQA@mail.gmail.com> (raw)
In-Reply-To: <DB6PR08MB2806AA39B76718817EA392A48B770@DB6PR08MB2806.eurprd08.prod.outlook.com>
On 20 June 2018 at 19:48, Evan Lloyd <Evan.Lloyd@arm.com> wrote:
> Hi Ard, Leif.
> I've noticed a number of comments like Ard's recent "We don't permit initialized automatic variables.",
> and similar changes have been made to Sami's AcpiView. Note: I'm not objecting to doing it the way maintainers prefer, which is why this is not a response.
>
> My understanding was that the CCS was changed some time back to remove the restriction on initializing variables (and I further think I remember Leif being a prime mover in that).
I don't remember, to be honest. But I think it is a stupid rule, and
so if we haven't already, I hope we can get rid of it.
IIRC, this limitation had something to do with a particularly nice
exhibit in the Tianocore toolchain museum that generated bigger
binaries for initialized automatic variables (as compared to
assignments performed separately). But let's not get into the
toolchain situation, shall we?
> If that is the case, I suspect the real problem is with ECC.py, which still whinges about it, so probably needs fixing.
> Can you confirm that I haven't got a firm grasp on the wrong end of the stick, please?
>
I could not find the limitation in the current version of the CCS, and
so whether it was there at /some/ point doesn't seem relevant to me.
We could file a bugzilla, and/or propose a patch that removes this
part from ECC.py (although I am not touching the python code if I can
avoid it)
next prev parent reply other threads:[~2018-06-20 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 17:48 Query about variable initialization Evan Lloyd
2018-06-20 18:03 ` Ard Biesheuvel [this message]
2018-06-20 18:57 ` Laszlo Ersek
2018-06-20 19:01 ` Ard Biesheuvel
2018-06-20 19:22 ` Andrew Fish
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+Gu-KCEVTsnZKOY7roUecwVv6hAixgvjZivSi0u0HAMUpQA@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