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 17:51:00 +0800 [thread overview]
Message-ID: <565EBF04.6050509@windriver.com> (raw)
In-Reply-To: <CAJTo0LaqebZA8akpdnAtFU2rJHsFX=1AxxtHWbq3JuEe5vBVyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On 12/02/2015 05:19 PM, Burton, Ross wrote:
>
> On 2 December 2015 at 05:06, Hongxu Jia <hongxu.jia@windriver.com
> <mailto:hongxu.jia@windriver.com>> wrote:
>
> The qemu didn't support '-march=corei7 -mtune=corei7' and
> gcc optimization level 3 '-O3' very well, in which the
> /usr/lib64/python2.7/test/test_md5.py and
> /usr/lib64/python2.7/test/test_sha.py failed.
>
> So we use gcc optimization level 2 to instead.
>
> YOCTO [# 8747]
>
>
> Has anyone decided if this is a bug in the compiler, or the Python
> code making assumptions that don't hold at -O3?
>
The root cause is the qemu didn't support gcc optimization level 3 very
well.
This fix is a workaround, and I file another defect to trace the root cause.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8748
//Hongxu
> Ross
[-- Attachment #2: Type: text/html, Size: 2418 bytes --]
next prev parent reply other threads:[~2015-12-02 9:51 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 [this message]
2015-12-02 9:57 ` Burton, Ross
2015-12-02 10:28 ` Hongxu Jia
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=565EBF04.6050509@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.