Ondřej Čertík

Plan from @kmr-srbh : Here is what is left to do: - [x] (Not needed.) Refactor handling `type_to_str()` to use `Variable` instead of `ttype`. We will use `ASRUtils::symbol_name(m_type_declaration)` for the...

I can reproduce this. Investigating. When ran via ctest it passes, when run manually (the same binary) it fails: ```console ~/.../integration_tests/test-llvm(main)$ ctest -R file_09 -V UpdateCTestConfiguration from :/home/ondrej/repos/lfortran/lfortran/integration_tests/test-llvm/DartConfiguration.tcl UpdateCTestConfiguration from...

What I mean is that I would focus on fixing #4617, and once you fix it (locally), then merge #4618 into it and make sure the CI still passes.

bc.. This is excellent! I currently don't need this, but let's get this in mpmath. The next time I need to solve some ODE, I'll look at that. p. Original...

See also https://github.com/lfortran/lfortran/pull/4206, which implemented the foundation.

I raised this to high priority, because the conda-forge osx-arm64 package upgraded to Clang 17 and does not seem to allow to install llvmdev=16. As a workaround I downgraded compilers...

Yes, we can build with LLVM 17, but only run very few tests that we managed to port so far. We still have about 100 places in the LLVM backend...

One idea I had was to create a dictionary of LLVM pointers and their types when we create them. Then when we "load" them, consult the dictionary and find the...

Yes. Ultimately we know the type in ASR, but the way the LLVM backend is structured sometimes we don't have this information because we have tons of utility functions that...

Current status: LLVM 10-19 passes all our integration tests and LLVM 17-19 pass all 3rd party tests except `fastGPT` and `stdlib` (LLVM 10-16 pass all our 3rd party code tests)....