From: Junling Zheng <zhengjunling@huawei.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Khem Raj <raj.khem@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "wangnan0@huawei.com" <wangnan0@huawei.com>
Subject: Re: [PATCH] arch-arm64.inc: Do not append aarch64 in MACHINEOVERRIDES
Date: Tue, 3 Mar 2020 22:13:46 +0800 [thread overview]
Message-ID: <dec3b3e2-e293-8107-bf97-34a0804ff4b0@huawei.com> (raw)
In-Reply-To: <41b7391039564f10a0c8b4f63eeb4274@XBOX03.axis.com>
On 2020/3/3 19:59, Peter Kjellerstedt wrote:
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-
>> bounces@lists.openembedded.org> On Behalf Of Junling Zheng
>> Sent: den 3 mars 2020 04:11
>> To: Khem Raj <raj.khem@gmail.com>; openembedded-
>> core@lists.openembedded.org
>> Cc: wangnan0@huawei.com
>> Subject: Re: [OE-core] [PATCH] arch-arm64.inc: Do not append aarch64 in
>> MACHINEOVERRIDES
>>
>> On 2020/3/3 2:29, Khem Raj wrote:
>>>
>>>
>>> On 3/2/20 9:11 AM, Junling Zheng wrote:
>>>> Currently, for arch-arm64, poky will append the MACHINEOVERRIDES with
>>>> "aarch64:", which has the higher priority than TRANSLATED_TARGET_ARCH.
>>>> So, for aarch64 big endian, the variable '<foo>_aarch64' will override
>>>> not only '<foo>', but also '<foo>_aarch64-be', thus we will get an
>>>> incorrect variable.
>>>>
>>>> Signed-off-by: Junling Zheng <zhengjunling@huawei.com>
>>>> ---
>>>> meta/conf/machine/include/arm/arch-arm64.inc | 2 --
>>>> 1 file changed, 2 deletions(-)
>>>>
>>>> diff --git a/meta/conf/machine/include/arm/arch-arm64.inc
>> b/meta/conf/machine/include/arm/arch-arm64.inc
>>>> index 53f4566815..32294bd218 100644
>>>> --- a/meta/conf/machine/include/arm/arch-arm64.inc
>>>> +++ b/meta/conf/machine/include/arm/arch-arm64.inc
>>>> @@ -4,8 +4,6 @@ require conf/machine/include/arm/arch-armv7ve.inc
>>>> TUNEVALID[aarch64] = "Enable instructions for aarch64"
>>>> -MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'aarch64', 'aarch64:', '' ,d)}"
>>>> -
>>>
>>> if its removed here, where is it being added for other machines,
>> question is, should we treat aarch64 as LE equivalent of aarch64_be
>>> or should be treated as common aarch64 and a new define like aarch64_le
>> defined.
>>>
>>
>> Currently, for arm64, we have aarch64_be to represent big endian, but no
>> overrides to represent little endian only.
>>
>> So, IMO, we should treat aarch64 as little enaian only, like arm and
>> armeb.
>>
>>>> # Little Endian base configs
>>>> AVAILTUNES += "aarch64 aarch64_be"
>>>> ARMPKGARCH_tune-aarch64 ?= "aarch64"
>
> Please, before removing "aarch64" from MACHINEOVERRIDES, add "armv8a" or
> similar. This is how it is done for the armv7* based chips. E.g., I would
> expect to see tune-cortexa53.inc have:
>
> MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'cortexa53', 'armv8a:', '' ,d)}"
>
arch-armv8a.inc has set "armv8a:" as overrides, and tune-cortexa53.inc requires arch-armv8a.inc.
> Which corresponds to how it is done for armv7*.
>
> At least we currently rely on being able to do, e.g.:
>
> COMPATIBLE_MACHINE = "aarch64|armv7a|armv7ve"
>
> and if you remove "aarch64" from MACHINEOVERRIDES, we need a suitable
> substitute.
>
> //Peter
>
>
> .
>
next prev parent reply other threads:[~2020-03-03 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 17:11 [PATCH] arch-arm64.inc: Do not append aarch64 in MACHINEOVERRIDES Junling Zheng
2020-03-02 18:29 ` Khem Raj
2020-03-02 21:34 ` Adrian Bunk
2020-03-03 19:27 ` Khem Raj
2020-03-03 3:10 ` Junling Zheng
2020-03-03 11:59 ` Peter Kjellerstedt
2020-03-03 13:05 ` Herve Jourdain
2020-03-03 13:33 ` Peter Kjellerstedt
2020-03-03 13:39 ` Adrian Bunk
2020-03-03 14:19 ` Peter Kjellerstedt
2020-03-03 19:21 ` Jeremy Puhlman
2020-03-03 14:13 ` Junling Zheng [this message]
2020-03-03 14:20 ` Peter Kjellerstedt
2020-03-03 14:39 ` Junling Zheng
2020-03-03 19:31 ` Khem Raj
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=dec3b3e2-e293-8107-bf97-34a0804ff4b0@huawei.com \
--to=zhengjunling@huawei.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=raj.khem@gmail.com \
--cc=wangnan0@huawei.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