On Mon, 2018-11-26 at 17:35 +0100, Martin Liška wrote: > On 11/26/18 5:19 PM, Matthias Klose wrote: > > On 26.11.18 13:20, Martin Liška wrote: > > > On 11/23/18 7:08 PM, Joseph Myers wrote: > > > > In the multiarch case, do you want > > > > <something>/include/finclude/<multiarch> or > > > > <something>/include/<multiarch>/finclude? (This is where I'd > > > > hope Debian > > > > / Ubuntu GCC people would comment.) > > > > > > Mathias can you please reply to this? > > > > this should not matter, as long as you use the multilib name, and the > > correct > > directory is used with the -m32/-m64/-mabi options. Are other compilers > > like a > > clang based compiler supposed to access this directory as well? > > I don't think so. > > > In that case > > the include directories should be documented.
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. Steve Ellcey sell...@cavium.com
