This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][RFC] Extend locations where to seach for Fortran pre-include.
- From: Thomas Koenig <tkoenig at netcologne dot de>
- To: Steve Ellcey <sellcey at caviumnetworks dot com>, Martin Liška <mliska at suse dot cz>, Matthias Klose <doko at debian dot org>, Joseph Myers <joseph at codesourcery dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>, Richard Biener <richard dot guenther at gmail dot com>, "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>, Toon Moene <toon at moene dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 27 Nov 2018 22:11:47 +0100
- Subject: Re: [PATCH][RFC] Extend locations where to seach for Fortran pre-include.
- References: <aed9a8c7-8d7b-b9e5-73a8-bb44acf144f8@suse.cz> <2913f91265696d2b6557037da018e126e63e19fe.camel@caviumnetworks.com>
Am 27.11.18 um 17:22 schrieb Steve Ellcey:
Why wouldn't clang (flang) want to use the same mechanism as
GCC/gfortran? I know there is some interest/work going on here for
flang and we would like a consistent way to use pre-includes to define
SIMD vector functions in both gfortran and flang. I think this should
be documented so flang and other compilers can use it. Even if no
other compilers did use it I think it should be documented because it
crosses project/package boundries, i.e. it is created by glibc and used
by gfortran.
Absolutely.
As soon as this is committed, we should document all the
specifics in the gfortran manual.
Regards
Thomas