[clang] [flang] [llvm] [openmp] [flang][driver] rename flang-new to flang (PR #110023)
@@ -339,11 +335,11 @@ just added using your new frontend option. ## CMake Support As of [#7246](https://gitlab.kitware.com/cmake/cmake/-/merge_requests/7246) -(and soon to be released CMake 3.24.0), `cmake` can detect `flang-new` as a +(and soon to be released CMake 3.24.0), `cmake` can detect `flang` as a hakostra wrote: 1. A search in the CMake repository revel that `flang-new` only appear in testcases and ci-related code - not in any code that eventually end up in CMake. This indicate that the name `flang-new` is not a magic token for CMake to recognize LLVM Flang. 2. I think that [this is the merge](https://gitlab.kitware.com/cmake/cmake/-/merge_requests/7246) that first introduced LLVM Flang to CMake. It seems like the check is through preprocessor macros defined by the different compilers. See [`Modules/CMakeFortranCompilerId.F.in`](https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules/CMakeFortranCompilerId.F.in) in the CMake sources. https://github.com/llvm/llvm-project/pull/110023 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [flang] [llvm] [openmp] [flang][driver] rename flang-new to flang (PR #110023)
hakostra wrote: I use `-DCMAKE_INSTALL_PREFIX=` as an argument to `cmake` and `ninja install` - that gives the layout above. https://github.com/llvm/llvm-project/pull/110023 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
[clang] [flang] [llvm] [openmp] [flang][driver] rename flang-new to flang (PR #110023)
hakostra wrote: I have freshly compiled and installed LLVM flang after the rename. I have: ``` $ ll flang* lrwxrwxrwx 1 hakostra hakostra 8 okt. 15 17:03 flang -> flang-20* -rwxr-xr-x 1 hakostra hakostra 176517648 okt. 23 12:03 flang-20* lrwxrwxrwx 1 hakostra hakostra 5 okt. 23 12:13 flang-new -> flang* $ ll clang* lrwxrwxrwx 1 hakostra hakostra 8 okt. 15 17:03 clang -> clang-20* lrwxrwxrwx 1 hakostra hakostra 5 okt. 23 12:13 clang++ -> clang* -rwxr-xr-x 1 hakostra hakostra 156923176 okt. 23 11:49 clang-20* ``` so `flang-20` and `clang-20` are the actual binaries, `flang` and `clang` are symlinks to these. Also, on my system, `/usr/bin/gcc` is just a symlink to whatever `gcc` version I have, for in my case `/usr/bin/gcc-13`. Same for `gfortran`. So it's the same naming scheme. This is intended behavior. If `flang` was the name of the binary and `flang-20` the symlink, it would not be possible to have several versions installed in besides each other. https://github.com/llvm/llvm-project/pull/110023 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
