* Orion Poplawski: > While poking at building openmpi with clang, I started wondering about > flang and some things: > > * Should %set_build_flags set FC? I think it should since it sets FCFLAGS. I see that FC is actually documented for GNU Make, so it makes sense if we want to go in that direction. > * Is flang-new even worth bothering with? See the following configure > check: > > configure:32655: flang-new -c -O2 -flto -fexceptions -g > -grecord-gcc-switches -pipe -Wall -Werror=format-security > -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS --config > /usr/lib/rpm/redhat/redhat-hardened-clang.cfg > -fstack-protector-strong -m64 -mtune=generic > -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection > -I/usr/lib64/gfortran/modules conftest.F >&5 > flang-new: warning: argument unused during compilation: '-fexceptions' > flang-new: warning: argument unused during compilation: '-g' > flang-new: warning: argument unused during compilation: > '-grecord-command-line' > flang-new: warning: argument unused during compilation: '-Wall' > flang-new: warning: argument unused during compilation: > '-Wp,-D_FORTIFY_SOURCE=2' > flang-new: warning: argument unused during compilation: > '-Wp,-D_GLIBCXX_ASSERTIONS' > flang-new: warning: argument unused during compilation: > '-fstack-protector-strong' > flang-new: warning: argument unused during compilation: '-mtune=generic' > flang-new: warning: argument unused during compilation: > '-fasynchronous-unwind-tables' > flang-new: warning: argument unused during compilation: > '-fstack-clash-protection' > flang-new: warning: argument unused during compilation: > '-fcf-protection=full' > error: Only `-Werror` is supported currently. > > Of particular note is ignoring the '-g' option. I can't find documentation on the supported options, and --help is not particularly illuminating. Maybe flang-new follows the option syntax of some other Fortran compiler and not gfortran? > I started poking at implementing this in redhat-rpm-config, but it > seems pretty tricky as for the most part we seem to assume that every > compiler can accept the same set of flags. > > This also bites us if we try to use gfortran with clang as I end up > with it trying to use the clang config. Yes, if we enable flang, gfortran will not be able to use those flags. Alternatively we can treat Fortran like Go and not control the compiler by toolchain settings. Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
