CI: Add experimental LFortran support#316
Conversation
LFortran correctly identified/reported that the arguments to MAX are all required to have the same type and kind
Identified via harmless LFortran warning, but worth fixing regardless
Ideally this would be a GitHub configuration variable, but there appears to be no reliable way to set a configuration variable that will reliably be inherited across repo forks, regardless of organization.
Also: * Workaround ISO_Fortran_binding.h missing from LFortran installs (issue 11079) * Factor curl options
|
Let me know if you need any fixes in LFortran. We'll iterate on the usage and command-line options. We'll change some of the defaults over time to make it easy to use. |
Thanks @certik ! I look forward to continuing our productive partnership, and helping to support LFortran's growth and eventual deployment of multi-image features! |
There are NO command changes in this commit, simply code motion and addition of section comments.
|
Thank your for using LFortran and giving us feedback, this is super helpful for us. |
|
@certik would you be willing to add additional tags on the LFortran container package to correspond to versioned releases? We have CI in multiple projects (and now this one, after this PR) relying on an LFortran DockerHub container that @PHHargrove kindly builds for us after each LFortran release, but it would save some steps if LFortran just provided release containers directly. |
|
Yes, we can do that. What exactly do we need to do? |
Issue entered: lfortran/lfortran#11100 |
3 participants
Minor script and code adjustments to accommodate LFortran version 0.62 and latest, which are now capable of building Caffeine (under the right conditions). Add LFortran to CI on Linux to help prevent bitrot. LFortran support remains deliberately undocumented for now.
Also deploy some factorization in the workflow definition file to ease maintenance.