Rebuild for flang 19 #250
Rebuild for flang 19 #250
Conversation
TL;DR: We are trying to switch our Fortran compilers on windows to flang. This is not 100% guaranteed to work, but should be fine in the majority of cases. The new LLVM-based flang has become mature enough that it should be possible to broadly switch over our Fortran compilers on windows to it (until now we only had an ancient pre-LLVM flang 5, or alternatively the GCC-based `m2w64_fortran`). As such, this PR attempts to homogenize any use of `m2w64_fortran` and other `m2w64_*` compilers to our default stack (which would then be MSVC + flang on windows), with the exception of feedstocks for R-packages, which stay on the `m2w64_` compilers. Recipes that have hard-coded expectations about the name of the fortran compiler will need to adjust to use `%FC%` or `flang-new` for the compiler name. Similarly, you may need to change the linker to `%LD%` or use `lld-link`. It is also possible that you run into compilation errors due to differences in compiler behaviour, bugs or as-yet unimplemented features. In case of compilation errors due to stricter default language standards, you should be able to fix things by passing `-std=legacy` to `FFLAGS`. If you have problems with this PR, feel free to ping the @c-f/flang-activation team. In case you have convinced yourself that flang really is not ready yet to be used to compile a given feedstock, you may also close this migrator PR.
…nda-forge-pinning 2025.01.21.20.56.13
regro-cf-autotick-bot
requested review from
SylvainCorlay,
astrofrog,
davidbrochart,
gillins,
groutr,
hmaarrfk,
jakirkham,
marcelotrevisani,
ocefpaf,
scopatz,
varlackc and
zklaus
as code owners
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12897727961. Examine the logs at this URL for more detail. |
|
we should move on to 1.14.5 and potentially backport the UTF-8 fix for windows. |
|
I don't think this PR is doing anything yet (I see no fortran code being compiled in the logs). The unix-side has |
|
Hey, looks like 1.14.6 just came out and it seems like it has reverted the breaking utf-8 changes of 1.14.4 and 1.14.5. Maybe jump straight to this release? https://github.com/HDFGroup/hdf5/releases/tag/hdf5_1.14.6 |
|
A PR taking and improving on the changes from here would help! not sure when I’ll have time to look at it! |
This PR has been triggered in an effort to update flang19.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
Here are some more details about this specific migrator:
If this PR was opened in error or needs to be updated please add the
bot-rerunlabel to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun botin a PR comment to have theconda-forge-adminadd it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/12897362290 - please use this URL for debugging.