Editing User:Avbm

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 30: Line 30:
== O: Only out of interest ==
== O: Only out of interest ==
I guess I have covered most of the topics above. My two main gripes with octave are:
I guess I have covered most of the topics above. My two main gripes with octave are:
*Not all of the image processing built-in functions are not supported including some of the more commonly used ones like the wiener filter
*Not all of the image processing built-in functions are not supported including some of the more commonly used ones like the weiner filter
*Octave is much slower than Matlab especially for non-vectorized code (which have many loops)
*Octave is much slower than Matlab especially for non-vectorized code (which have many loops)


Line 48: Line 48:
I am quite sure that I will have enough time for only <b>one</b> of the two and am leaning more towards JIT since that will be more useful in general.
I am quite sure that I will have enough time for only <b>one</b> of the two and am leaning more towards JIT since that will be more useful in general.


My planned schedule is:
*May 28 - June 16: Get acquainted with llvm and familiarize myself with Octave's Abstract Syntax Tree(AST) and Single Static Assignment(SSA) property of intermediate representation(IR). Also seperate the various parts of the code into smaller functional blocks and start on llvm 3.2 compatibility.(Some work has already been done on 3.2 compatibility)
*June 17 - July 29: Make the current JITC code compatible with llvm 3.2 and work on making an llvm IR for a matrix.
*July 30 - August 30: Convert an octave Matrix IR to llvm IR and work on getting everything together.
*Sept 1 - Sept 14: Clean up the code, iron out the creases and work on final report.


 
[[Category:Summer of Code 2013 Applicants]]
[[Category:2013]]
[[Category:Applicants]]
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)