pawosm-arm wrote: @Meinersbur, @tblah I need some suggestions on how to continue with this PR. There seem to be a deadlock situation here:
1. We do not want to modify the flang test suite configuration files, and follow the way the training code is provided for optimizing clang, which is to keep the training suite and its configuration files in a separate `perf-training` directory. 2. We want to use a decent amount of Fortran code to train the optimizer with, but we cannot follow the way `clang/utils/perf-training/llvm-support/build.test` reuses one of the clang codebase `Makefile` targets (namely, `LLVMSupport`, which offers decent amount of C++ code to train with), as there is simply not enough Fortran code in the flang codebase 3. We cannot reuse flang test suite (which offers a decent amount of Fortran code to train with) from `perf-training`, as the `check-...` targets are not available before the executable binaries (optimized or not) are available. For that reason we would have to modify flang test suite configuration files and it contradicts with the point 1. I need some inspiration on how to escape from this deadlock. https://github.com/llvm/llvm-project/pull/198863 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
