Student: Anutosh Bhat
Project: Implementing Symbolic Algorithms as a part of ASR
Organisation: Python Software Foundation
Mentor: Ondřej Čertík
Proposal: GSoC 23 Proposal
Weekly Blogs: anutosh491.github.io
This file contains hidden or 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
| (TranslationUnit | |
| (SymbolTable | |
| 1 | |
| { | |
| __main__: | |
| (Module | |
| (SymbolTable | |
| 2 | |
| { | |
| __main____global_statements: |
This file contains hidden or 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
| #include <libasr/asr.h> | |
| #include <libasr/containers.h> | |
| #include <libasr/exception.h> | |
| #include <libasr/asr_utils.h> | |
| #include <libasr/asr_verify.h> | |
| #include <libasr/pass/replace_symbolic.h> | |
| #include <libasr/pass/pass_utils.h> | |
| #include <libasr/pass/intrinsic_function_registry.h> | |
| #include <vector> |
This file contains hidden or 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
| So I've made enough progress and I currently have enough understanding of what's | |
| happening to share it with you. I can't invest more time on this than what I've | |
| already be doing, hopefully this is going to put you on track. | |
| = Why do we have this -isystem /usr/include? | |
| emcmake passes a toolchain file (cmake/Modules/Platform/Emscripten.cmake) to | |
| cmake that informs it about the toolchain. In the process it sets | |
| CMAKE_CROSSCOMPILING=ON. |
This file contains hidden or 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
| execution.hpp | |
| /************************************************************************************ | |
| * Copyright (c) 2023, xeus-cpp contributors * | |
| * Copyright (c) 2023, Johan Mabille, Loic Gouarin, Sylvain Corlay, Wolf Vollprecht * | |
| * * | |
| * Distributed under the terms of the BSD 3-Clause License. * | |
| * * | |
| * The full license is in the file LICENSE, distributed with this software. * | |
| ************************************************************************************/ |
This file contains hidden or 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
| //===----------------- Wasm.cpp - Wasm Interpreter --------------*- C++ -*-===// | |
| // | |
| // Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. | |
| // See https://llvm.org/LICENSE.txt for license information. | |
| // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception | |
| // | |
| //===----------------------------------------------------------------------===// | |
| // | |
| // This file implements interpreter support for code execution in WebAssembly. | |
| // |
Hi All,
I’m Anutosh, a core developer on clang/clang-repl and part of Project Jupyter. Previously I was a member at another LLVM-based Fortran compiler, LFortran .
I had presented the above idea in the previous flang biweekly meeting and was advised to frame a RFC for the same.
- The Fortran ecosystem still lacks a modern, interactive workflow—something equivalent to a REPL or an Interpreter that many other LLVM-based languages now support. This limits rapid prototyping, teaching, exploratory numerical work, and smooth integration with tools like Jupyter.