Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

D5.4: Make Pythran typing better to improve error information. #117

Closed
minrk opened this issue Sep 8, 2015 · 13 comments
Closed

D5.4: Make Pythran typing better to improve error information. #117

minrk opened this issue Sep 8, 2015 · 13 comments

Comments

@minrk
Copy link
Contributor

@minrk minrk commented Sep 8, 2015

Pythran is a Python to C++ compiler for a subset of the Python language, with a focus on scientific computing, which takes advantage of multi-cores and SIMD instruction units. Given the importance of Python in the OpenDreamKit ecosystem, Pythran is one of the promising building blocks for high performance mathematical computing.

This deliverable is about enhancing the Pythran compiler to provide better user feedback when a type error is meet, by extracting and taking advantage of fine grain type information. The optimizations developed in this context are a more accurate version of identifier binding that increases the scope of Pythran valid input. Second, an unsound type checker has been developed and integrated in the 0.8 version of the Pythran compiler. It provides usable, meaningful feedback to users in case of type error, instead of internal compiler errors. These two steps make it easier to write computation-intensive kernels to be compiled by Pythran.

@minrk minrk added this to the D5.4 milestone Sep 8, 2015
@nthiery nthiery modified the milestones: Month 12: 2016-08-31, D5.4 Mar 22, 2016
@serge-sans-paille
Copy link
Contributor

@serge-sans-paille serge-sans-paille commented Apr 19, 2016

Nice step toward better typing in pythran: Better identifier binds-to computation.

http://serge-sans-paille.github.io/pythran-stories/identifier-binding-computation.html

@bpilorget
Copy link
Contributor

@bpilorget bpilorget commented Aug 30, 2016

Deliverable to be postponed

@bpilorget
Copy link
Contributor

@bpilorget bpilorget commented Aug 30, 2016

The README gives info on how to write deliverables (scroll down): https://github.com/OpenDreamKit/OpenDreamKit

@serge-sans-paille
Copy link
Contributor

@serge-sans-paille serge-sans-paille commented Aug 30, 2016

@bpilorget
Copy link
Contributor

@bpilorget bpilorget commented Nov 21, 2016

@ClementPernet and @serge-sans-paille
This deliverable is due for February 2017(No postponement allowed!!)

@serge-sans-paille
Copy link
Contributor

@serge-sans-paille serge-sans-paille commented Nov 21, 2016

@serge-sans-paille
Copy link
Contributor

@serge-sans-paille serge-sans-paille commented Dec 28, 2016

Deliverable sent to logilab, merged into the trunk of pythran and advertise in a blogpost http://serge-sans-paille.github.io/pythran-stories/from-pythran-import-typing.html

@nthiery
Copy link
Contributor

@nthiery nthiery commented Jan 5, 2017

Great, there just remain to write the report. Who is handling this? @serge-sans-paille ? @fcayre ?

@kohlhase kohlhase mentioned this issue Jan 16, 2017
19 of 19 tasks complete
@nthiery
Copy link
Contributor

@nthiery nthiery commented Feb 1, 2017

Ping! Since it's jut a matter of a short report, it would be good to get this done.

@serge-sans-paille
Copy link
Contributor

@serge-sans-paille serge-sans-paille commented Feb 1, 2017

Woops missed that one. I'll write the report, @nthiery can you just point me to the place I should put it?

@nthiery
Copy link
Contributor

@nthiery nthiery commented Feb 2, 2017

@nthiery
Copy link
Contributor

@nthiery nthiery commented Feb 6, 2017

Dear M18 deliverable leaders,

Just a reminder that reports are due for mid-february, to buy us some time for proofreading, feedback, and final submission before February 28th. See our README for details on the process.

In practice, I'll be offline February 12-19, and the week right after will be pretty busy. Therefore, it would be helpful if a first draft could be available sometime this week, so that I can have a head start reviewing it.

Thanks in advance!

@nthiery
Copy link
Contributor

@nthiery nthiery commented Feb 10, 2017

Final report, as of 28859db submitted on the EU portal.

Thank you Serge for this nice improvement to Pythran and its report!

@nthiery nthiery closed this Feb 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.