From: Mark Hatle <mark.hatle@windriver.com>
To: Robert Yang <liezhi.yang@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: Richard Purdie <richard.purdie@intel.com>
Subject: Re: [PATCH 1/1] gcc-multilib-config: make aarch64 support multilib
Date: Thu, 5 Nov 2015 07:43:33 -0600 [thread overview]
Message-ID: <563B5D05.9060609@windriver.com> (raw)
In-Reply-To: <88477fa50093b85e65b17c746a637c7259b87018.1446711613.git.liezhi.yang@windriver.com>
On 11/5/15 2:20 AM, Robert Yang wrote:
> Fixed:
> MACHINE = qemuarm64
> require conf/multilib.conf
> MULTILIBS = "multilib:lib32"
> DEFAULTTUNE_virtclass-multilib-lib32 = "armv7at-neon"
>
> $ bitbake core-image-minimal -cpopulate_sdk
>
> WARNING: gcc multilib setup is not supported for TARGET_ARCH=aarch64
> WARNING: gcc multilib setup is not supported for TARGET_ARCH=aarch64
>
> [YOCTO #8638]
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> meta/recipes-devtools/gcc/gcc-multilib-config.inc | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-multilib-config.inc b/meta/recipes-devtools/gcc/gcc-multilib-config.inc
> index 1c0a45a..a0a2ac0 100644
> --- a/meta/recipes-devtools/gcc/gcc-multilib-config.inc
> +++ b/meta/recipes-devtools/gcc/gcc-multilib-config.inc
> @@ -29,6 +29,9 @@ python gcc_multilib_setup() {
> bb.utils.remove(build_conf_dir, True)
> ml_globs = ('%s/*/t-linux64' % src_conf_dir,
> '%s/*/linux64.h' % src_conf_dir,
> + '%s/aarch64/t-aarch64' % src_conf_dir,
> + '%s/aarch64/aarch64.h' % src_conf_dir,
> + '%s/aarch64/aarch64-cores.def' % src_conf_dir,
> '%s/*/linux.h' % src_conf_dir,
> '%s/linux.h' % src_conf_dir)
>
> @@ -130,6 +133,8 @@ python gcc_multilib_setup() {
> 'mips64' : ['gcc/config/mips/t-linux64'],
> 'powerpc' : ['gcc/config/rs6000/t-linux64'],
> 'powerpc64' : ['gcc/config/rs6000/t-linux64'],
> + 'aarch64' : ['gcc/config/aarch64/t-aarch64'],
> + 'arm' : ['gcc/config/aarch64/t-aarch64'],
> }
>
> gcc_header_config_files = {
> @@ -140,6 +145,8 @@ python gcc_multilib_setup() {
> 'mips64' : ['gcc/config/mips/linux.h', 'gcc/config/mips/linux64.h'],
> 'powerpc' : ['gcc/config/rs6000/linux64.h'],
> 'powerpc64' : ['gcc/config/rs6000/linux64.h'],
> + 'aarch64' : ['gcc/config/aarch64/aarch64.h'],
> + 'arm' : ['gcc/config/aarch64/aarch64.h'],
> }
I'm not sure the above is correct in this case. As I believe GCC treats aarch64
and arm as different architectures unlike MIPS, Power and IA32.
In this case, I would expect two specific cross compilers to be generated, one
for armv7 and one for aarch64, instead of a combination single compiler that
understand both.
So in this case, it might be better to have an exception to the warning
message... (unless I'm wrong, in which case this IS likely a correct fix....)
Hopefully Khem and/or Richard will be able to comment as they are more familiar
with this code path.
>
> libdir32 = 'SYSTEMLIBS_DIR'
>
next prev parent reply other threads:[~2015-11-05 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 8:20 [PATCH 0/1] gcc-multilib-config: make aarch64 support multilib Robert Yang
2015-11-05 8:20 ` [PATCH 1/1] " Robert Yang
2015-11-05 13:43 ` Mark Hatle [this message]
2015-11-06 3:01 ` Robert Yang
2015-11-06 5:35 ` Khem Raj
2015-11-06 14:41 ` Mark Hatle
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=563B5D05.9060609@windriver.com \
--to=mark.hatle@windriver.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@intel.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