-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Sync libasr
with LPython
#2837
Sync libasr
with LPython
#2837
Conversation
82d5ad8
to
e6a9544
Compare
@czgdp1807 The WAT tests are good except two reference tests about bindC in wasm. I think these fail because in LPython we updated the wasm backend to use bindJS instead of bindC. I would ideally fix this in a separate PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems you are still fixing the sync here, ping me once this is ready.
for (size_t i = 0; i < strlen(*x); i ++) { | ||
*x = (char*) malloc((strlen(y) + 1) * sizeof(char)); | ||
_lfortran_string_init(strlen(y) + 1, *x); | ||
for (size_t i = 0; i < strlen(*x); i++) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this change is needed for LPython.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some tests in LPython fail because the logic is incorrect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, this seems to be related to Strings, so I will work on this in a new PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please create an issue so we do not forget.
For now, what should I do with |
I am unsure if we are allowed to commit these to main branch, but I created an issue for it #2839. |
Since it is a sync PR, I think it is good to support the above issue in a separate PR. |
e6a9544
to
147d8b9
Compare
@@ -938,7 +938,7 @@ RUN(NAME bits_04 LABELS gfortran llvm) | |||
RUN(NAME bits_05 LABELS gfortran llvm) | |||
RUN(NAME bits_06 LABELS gfortran llvm fortran) | |||
RUN(NAME cpu_time_01 LABELS gfortran llvm) | |||
RUN(NAME cpu_time_02_wasm LABELS wasm) | |||
# RUN(NAME cpu_time_02_wasm LABELS wasm) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is going on in this test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Shaikh-Ubaid will fix this in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, it's this: #2839
I can't see any |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks good, I don't see any blocker here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for doing this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. It looks good to me!
fa0d7cb
to
a0d2a32
Compare
lcompilers/lpython#2410