-
Notifications
You must be signed in to change notification settings - Fork 54
Add compilers to roadmap #191
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -147,6 +147,22 @@ Desired features include: | |||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
**Expected outcomes:** fpm can generate source code distributions of packages that can be build using CMake and/or Meson. | ||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
## Improving Compilers | ||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
The aim of this project is to create and maintain an open source Fortran compiler as a community, here is a non-exhaustive list of (independent) features: | ||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
* compile all Fortran projects to binaries | ||||||||||||||||||||||||||||
* work interactively (Jupyter notebooks) | ||||||||||||||||||||||||||||
* in the browser | ||||||||||||||||||||||||||||
* works as the foundation for linters, VSCode language integration and documentation generators | ||||||||||||||||||||||||||||
* runs well on modern hardware (CPU, GPU, ...) | ||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
There are three open source compilers under development: | ||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
* LFortran: https://lfortran.org/ | ||||||||||||||||||||||||||||
* Flang: https://flang.llvm.org/docs/ | ||||||||||||||||||||||||||||
* GFortran: https://gcc.gnu.org/wiki/GFortran | ||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
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. I would consider adding the actual projects and deliverables we have in mind for these (at least for LFortran which you control): https://github.com/fortran-lang/fortran-lang.org/wiki/GSoC-2022-Project-ideas#language-server For the LSP stuff I would add some summaries from the discussion with the vscode-cpptools devs and email conversations. I will dig them up at a later point
Suggested change
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. @certik wanna have a look and tell me if I forgot something? 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. This requires a design discussion. I would not recommend parsing the f2py output, because it means supporting that syntax, which complicates maintenance. For f2py's application, I think it's better to just parse Fortran itself, and possibly annotate with comments, both of which we can parse. Also adding ASR nodes must be done carefully. We try avoiding adding nodes which are only used by one tool, as opposed to all of Fortran (or other languages). 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 me try to write down a roadmap, for the next half a year, which effectively is to compile "fpm". 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. We can remove the F2PY section if that makes things simpler and then iterate on the roadmap at a later point. I simply gathered the descriptions of the GSoC projects that had not been completed in 2022 |
||||||||||||||||||||||||||||
## [Modern Fortran for Visual Studio Code](https://github.com/fortran-lang/vscode-fortran-support) | ||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||
### Integration with the Fortran Package Manager and CMake | ||||||||||||||||||||||||||||
|
Uh oh!
There was an error while loading. Please reload this page.