-
Notifications
You must be signed in to change notification settings - Fork 166
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
Fix ASR verify pass error while using Interactive #2706
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
f71b4a7
skipping function verification of Interactive ABI
Vipul-Cariappa 36930eb
function verify checks for empty body
Vipul-Cariappa 25e047e
intrinsic function's body & dependency left unchanged
Vipul-Cariappa 7cda8e3
Fix ASR verify pass error while using Interactive
Vipul-Cariappa 4a476b6
updated tests
Vipul-Cariappa 5d1fe44
fix typos
Vipul-Cariappa 5469ddf
update cmake to copy runtime python files to build dir
Vipul-Cariappa d899b15
fix test for the changes in main
Vipul-Cariappa 2896a23
fix indentation for windows
Vipul-Cariappa ef4cf7c
fix for windows
Vipul-Cariappa 06c7dd1
undo indentations
Vipul-Cariappa e65cfe1
indentation fix
Vipul-Cariappa b29338d
Merge branch 'main' into dev
Vipul-Cariappa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -116,7 +116,7 @@ std::string read_file(const std::string &filename) | |
std::vector<char> bytes(filesize); | ||
ifs.read(&bytes[0], filesize); | ||
|
||
return std::string(&bytes[0], filesize); | ||
return replace(std::string(&bytes[0], filesize), "\r\n", "\n"); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's open an issue that our tokenizer/parser should be updated/fixed to produce the same tokens/parse-tree on windows and unix. |
||
} | ||
|
||
std::string parent_path(const std::string &path) { | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1143,4 +1143,3 @@ def list(s: str) -> list[str]: | |
for i in range(len(s)): | ||
l.append(s[i]) | ||
return l | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Not sure if its a good idea to copy these. As of now, where does
lpython
look for these? Can we updatelpython
to look into the correct location?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.
Copying is the safest thing to do. Right now it uses relative path from the executable's location to figure out the runtime file's path.
The reason I say it is a safe option is because the user building the LPython may set the
CMAKE_CURRENT_BINARY_DIR
to a completely different folder. For example, in Windows, I may want to store the source files inD
drive and the compiled executable inC
drive.