All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tsai, Matt" <matt.tsai@thermofisher.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Yocto standard SDK machine dependent compiler options
Date: Fri, 22 Mar 2019 01:39:48 +0000	[thread overview]
Message-ID: <BYAPR07MB55899CB22B0FA7D9988591DD92430@BYAPR07MB5589.namprd07.prod.outlook.com> (raw)

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

Hi all,

I have built the standard Yocto SDK using the "bitbake <image> -c populate_sdk" command. I have some questions related to the generated toolchain. I wonder if I can get my doubts cleared here.

Here are my hardware/software info:
Target platform is Freescale p2020 rdb.
Yocto versions used to build the SDK:
Poky: tag "sumo-19.0.1"
Meta-freescale: sumo branch commit hash: 407c6cf408969445031a492e2d25e0e2749582ea (on Oct. 4, 2018)

Questions:

  1.  The generated SDK contains a script environment-setup-ppce500v3-poky-linux-gnuspe to source some machine-dependent compiler options. I assume these are good (if not optimal) options to use when I build my applications. And the generated code is able to make use of two cores and other hardware features of the p2020 processor. Is this correct? What is the effect if I do not add these -m options?



I list some of the compiler/assembler options below:

CC="powerpc-poky-linux-gnuspe-gcc  -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double --sysroot=$SDKTARGETSYSROOT"

CXX="powerpc-poky-linux-gnuspe-g++  -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double --sysroot=$SDKTARGETSYSROOT"

CPP="powerpc-poky-linux-gnuspe-gcc -E  -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double --sysroot=$SDKTARGETSYSROOT"

AS="powerpc-poky-linux-gnuspe-as "

LD="powerpc-poky-linux-gnuspe-ld  --sysroot=$SDKTARGETSYSROOT"



  1.  If these -m options are not good to use, do I need to build the compilers with different configurations? Or add different machine dependent options?
  2.  Are there any documents/references of these machine-dependent options besides the -target-help from the command line?


If this not the right place for the questions, please kindly point me to the right source.

Thank you very much for the help!


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

             reply	other threads:[~2019-03-22  3:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  1:39 Tsai, Matt [this message]
2019-03-22  5:34 ` Yocto standard SDK machine dependent compiler options Zhenhua Luo
2019-03-22 16:55   ` Tsai, Matt
2019-03-24 13:23     ` Zhenhua Luo

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=BYAPR07MB55899CB22B0FA7D9988591DD92430@BYAPR07MB5589.namprd07.prod.outlook.com \
    --to=matt.tsai@thermofisher.com \
    --cc=meta-freescale@yoctoproject.org \
    /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.