On 16/05/2017, 16.45, "Richard Purdie"
wrote:
On Tue, 2017-05-16 at 16:18 +0300, Markus Lehtonen wrote:
> This patchset makes it possible to make a PGO (profile-guided-
> optimization) build of python. This version of the patchset is almost
> identical to v1 submitted back in F
On 05/16/2017 05:07 PM, Markus Lehtonen wrote:
You're probably right. There's not much use in churning
soon-to-be-deprecated Python 2.x. I will submit a new patchset for
Python 3.x only. Python 2.x could be added later if deprecation
wouldn't happen for some reason.
The deprecation is not a si
On 16/05/2017, 16.23, "Alexander Kanavin"
wrote:
On 05/16/2017 04:18 PM, Markus Lehtonen wrote:
> This patchset makes it possible to make a PGO
(profile-guided-optimization)
> build of python. This version of the patchset is almost identical to v1
> submitted back in February, w
On Tue, 2017-05-16 at 16:18 +0300, Markus Lehtonen wrote:
> This patchset makes it possible to make a PGO (profile-guided-
> optimization) build of python. This version of the patchset is almost
> identical to v1 submitted back in February, with these changes:
> - rebased on top of latest oe-core m
On 05/16/2017 04:18 PM, Markus Lehtonen wrote:
This patchset makes it possible to make a PGO (profile-guided-optimization)
build of python. This version of the patchset is almost identical to v1
submitted back in February, with these changes:
- rebased on top of latest oe-core master
- exclude pr
This patchset makes it possible to make a PGO (profile-guided-optimization)
build of python. This version of the patchset is almost identical to v1
submitted back in February, with these changes:
- rebased on top of latest oe-core master
- exclude profile data for Modules/posixmodule of Python 2.7
