-
Notifications
You must be signed in to change notification settings - Fork 397
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
BenefitInliner phase 3/3: Classes for doing nested knapsack algorithm and the inlining. #5509
Conversation
23d0143
to
8b45e1a
Compare
c8c9f9f
to
3a7d796
Compare
Hi @jdmpapin, would you mind to review this pull request? Since this is the next phase of #5508 and there is no assignees now. Please note this PR has been finished now. The title shows it is WIP because I'm not the original contributor and don't have the permission to change it. Thank you in advance!😊 |
hey @jdmpapin , @vijaysun-omr I was wondering if you folks had a chance to review this PR? Unlike what the title suggests (which we don't have edit rights to change), it's no longer WIP and it is ready to be reviewed now that Phase 2 has been merged. |
I'll review soon |
Thanks @jdmpapin! |
I started reviewing yesterday. Between other things, I hope to be done the review in the next few days |
Thank you very much! |
Sorry again, trying to get back to this soon |
ee0389c
to
6cd0329
Compare
Hi @jdmpapin, thank you for your review. I have finished resolving most review comments, except 4 comments still need some futher look since they may affect the core algorithm. I will finish those 4 comments ASAP and I will notify you once I finish. I also submmited finished part so you can start to review them if you want. I submitted changes with another commit for now. I will squash those commits to 1 commit and force push to the repo after all changes are accepted. |
67e07ce
to
2f3b33a
Compare
Hi @jdmpapin, I have made some new changes for the unsolved feedbacks. Could you please take a look? Thank you in advance. Please ignore the macOS build check was failed since it failed due to a known issue of porttest. |
2f3b33a
to
cdf7afb
Compare
cdf7afb
to
f57525f
Compare
Hi @jdmpapin, I have made some changes to the unresolved and new comments. Please take a look. |
f57525f
to
8a1fe11
Compare
Hi @jdmpapin, I fixed all new concerns. Please have a look. Thank you! |
Jenkins build all |
…ining. This is the phase 3/3 of the BenefitInliner contribution. * OMROptions.hpp, OMROptions.hpp: add new options for the BenefitInliner. * AbsVisitor.hpp, IDTBuilder.hpp, OMRIDTBuilder.hpp, OMRIDTBuilder.cpp: new class files for building IDT. * BenefitInliner.hpp, BenefitInliner.cpp, InliningProposal.hpp, InliningProposal.cpp: new class files for doing nested knapsack algorithm and inlining. Co-authored-by: Mingwei Li <[email protected]> Signed-off-by: Cijie Xia <[email protected]>
8a1fe11
to
8414472
Compare
Hi @jdmpapin,I forgot to remove |
Jenkins build all |
Hi @jdmpapin, seems almost all Jenkins build checks passed, excepts the macOS and linux riscv64. For macOS, the console shows:
this is a known issue related to #7181. For linux riscv64, the console shows:
looks like it is a silimar issue as mentioned at #5508 (comment), so I think this is also a known issue. So I think this PR should be ready to be merged. |
Hi @jdmpapin, I think this PR should be ready to be merged. Would you mind to take a look for the final approval? Thank you! |
Jenkins build riscv |
I expect UMA builds need updating for this (e.g. |
Hi @keithc-ca, I will open another issue and PR later to add the new source files to this makefile. However, I'm not very sure what the "UMA" stands for. I saw some issues and comments mentioned it, but I cannot find any more info about it. Could you please tell me where I can find more info about the "UMA builds" so I can check if there is any other file also needs update. |
"UMA" is short for "Universal Makefile Adapter"; see https://github.com/eclipse-openj9/openj9/blob/master/sourcetools/com.ibm.uma/com/ibm/j9/uma/Main.java#L34. In the context of OMR it involves using |
Thnak you Keith! I will take a look for this problem. |
Issue: #5488