All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ruslan Babayev" <ruslan@babayev.com>
To: Ross Burton <ross@burtonini.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] meson: use the more specific cpu arch in cross file
Date: Mon, 27 Jul 2020 12:03:29 -0700	[thread overview]
Message-ID: <CAOpYhv9MHvuDgU-Rrkn3cdyhge0y_wTtOQRuogMR46E-zQ-w6A@mail.gmail.com> (raw)
In-Reply-To: <CAAnfSTvFPFsSzimALDEGWQCrMRszViYWT7kqBbs3UrgRrfAN3w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

Hi Ross,

According to https://mesonbuild.com/Cross-compilation.html

There are two different values for the CPU. The first one is cpu_family. It
is a general type of the CPU. This should have a value from the CPU Family
table <https://mesonbuild.com/Reference-tables.html#cpu-families>. *Note* that
meson does not add el to end cpu_family value for little endian systems.
Big endian and little endian mips are both just mips, with the endian field
set approriately.

The second value is cpu which is a more specific subtype for the CPU.
Typical values for a x86 CPU family might include i386 or i586 and for arm
 family armv5 or armv7hl. Note that CPU type strings are very system
dependent. You might get a different value if you check its value on the
same machine but with different operating systems.
At the moment both 'cpu_family' and 'cpu' are being set to TARGET_ARCH
(like x86_64) in meson cross file.

TUNE_CCARSG usually contains the exact subfamily either as -march= or
-mcpu=

The meson_cpu function will use regex to search for -march and if that's
missing for -mcpu value. If both flags are missing it defaults to
TARGET_ARCH.

Ruslan


On Mon, Jul 27, 2020 at 3:52 AM Ross Burton <ross@burtonini.com> wrote:

> On Sun, 26 Jul 2020 at 02:56, Ruslan Babayev <ruslan@babayev.com> wrote:
> > 'cpu' unlike 'cpu_family' must be a more specific subtype for the CPU.
>
> Can you elaborate here some more?
>
> Ross
>

[-- Attachment #2: Type: text/html, Size: 5799 bytes --]

  reply	other threads:[~2020-07-27 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26  1:56 [PATCH] meson: use the more specific cpu arch in cross file Ruslan Babayev
2020-07-26  2:02 ` ✗ patchtest: failure for " Patchwork
2020-07-27 10:52 ` [OE-core] [PATCH] " Ross Burton
2020-07-27 19:03   ` Ruslan Babayev [this message]
2020-07-29 21:04     ` Ruslan Babayev
2020-07-30  4:55 ` Khem Raj
2020-07-30  6:12   ` Ruslan Babayev
2020-07-30  8:49     ` Richard Purdie

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=CAOpYhv9MHvuDgU-Rrkn3cdyhge0y_wTtOQRuogMR46E-zQ-w6A@mail.gmail.com \
    --to=ruslan@babayev.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.