[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    Re: [OE-core] [PATCH] meson: use the more specific cpu arch in cross file
From:       "Richard Purdie" <richard.purdie () linuxfoundation ! org>
Date:       2020-07-30 8:49:24
Message-ID: 93bb635493302c6cc46a40f2eb02e4af264ac2a5.camel () linuxfoundation ! org
[Download RAW message or body]

On Wed, 2020-07-29 at 23:12 -0700, Ruslan Babayev wrote:
> Currently we have both cpu_family and cpu set to TARGET_ARCH which is
> wrong. As mentioned before cpu is more specific. E.g where
> cpu_family='x86-64' cpu='nehalem'.
>   
> Projects using Meson can query for the host_machine.cpu() and expect
> a more specific CPU type.
> Here's one example:
> https://github.com/DPDK/dpdk/blob/74f4d6424da1297bd6e83dcb7bd84444ca8c59dd/config/meson.build#L69 

That logic looks like its basically being used to set -march. We
already set this.

Khem and Ross' question is to find out what is currently breaking that
needs this fix. In general for example, we have a much better idea of
what march should be set to in our uses cases.

Cheers

Richard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#141122): https://lists.openembedded.org/g/openembedded-core/message/141122
Mute This Topic: https://lists.openembedded.org/mt/75796683/4454766
Group Owner: openembedded-core+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  [openembedded-core@marc.info]
-=-=-=-=-=-=-=-=-=-=-=-


[prev in list] [next in list] [prev in thread] [next in thread]