From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] python: gcc optimization level 2
Date: Wed, 2 Dec 2015 18:28:14 +0800 [thread overview]
Message-ID: <565EC7BE.6060105@windriver.com> (raw)
In-Reply-To: <CAJTo0Lag5J+cytX8C+Z7b8dmX65MZWJBV6JXQt=Ocwy==szenA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On 12/02/2015 05:57 PM, Burton, Ross wrote:
>
> On 2 December 2015 at 09:51, Hongxu Jia <hongxu.jia@windriver.com
> <mailto:hongxu.jia@windriver.com>> wrote:
>
> The root cause is the qemu didn't support gcc optimization level 3
> very well.
>
>
> Oh, so the problem only appears in qemu if you enable tuning that is
> known to be broken in qemu?
Yes, since I tested qemux86/qemux86-64 with default tune, and everything
is ok.
> I don't think we should apply the Python workaround to oe-core as
> everyone will suffer for a configuration that is known to be broken
> (and isn't enabled in oe-core).
Trace the issue costs a lot of time, the original failure was invoking
'smart update' in qemu, and found out the python md5/sha checksum
output incorrect, and then found out qemu86-64 with corei7-64 did
not support gcc optimization level 3 '-O3' very well [YOCTO #8748]
BTW, boot the same image with virtualbox, everything is ok
//Hongxu
>
> Ross
[-- Attachment #2: Type: text/html, Size: 2658 bytes --]
next prev parent reply other threads:[~2015-12-02 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 5:06 [PATCH 0/1] fix python md5/sha checksum incorrect on qemu86-64 with corei7-64 as DEFAULTTUNE Hongxu Jia
2015-12-02 5:06 ` [PATCH 1/1] python: gcc optimization level 2 Hongxu Jia
2015-12-02 9:19 ` Burton, Ross
2015-12-02 9:51 ` Hongxu Jia
2015-12-02 9:57 ` Burton, Ross
2015-12-02 10:28 ` Hongxu Jia [this message]
2015-12-02 10:33 ` Burton, Ross
2015-12-08 7:12 ` 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=565EC7BE.6060105@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 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.