Generated files going to a different place now - intentional?

2024-08-17 Thread Thomas Koenig
Hi, when working on the first unsigned array intrinsics, I noticed something strange. With maintainer mode enabled, and the usual-style patch to include the generated functions (see below), I found that the files were regenerated in the build dir, under x86_64-pc-linux-gnu/libgfortran/generated

Re: [PATCH, gfortran] libgfortran: implement fpu-macppc for Darwin, support IEEE arithmetic

2024-08-17 Thread Sergio Had
Hi, If we are good at this point, could someone help with merging it? (I don’t have commit access, of course.) Sergey On Aug 14, 2024 at 21:30 +0800, Sergey Fedorov , wrote: > Thank you, Iain. > I have adjusted a longer line and added an intro sentence before changelog > record. > > > > > On We

Re: Generated files going to a different place now - intentional?

2024-08-17 Thread Thomas Koenig
Am 17.08.24 um 13:20 schrieb Thomas Koenig: when working on the first unsigned array intrinsics, I noticed something strange.  With maintainer mode enabled, and the usual-style patch to include the generated functions (see below), I found that the files were regenerated in the build dir, under x

Re: Generated files going to a different place now - intentional?

2024-08-17 Thread Thomas Koenig
Am 17.08.24 um 13:20 schrieb Thomas Koenig: --- a/libgfortran/m4/types.m4 +++ b/libgfortran/m4/types.m4 Yes, I now know that this is the wrong place (we could remove this, I think :-)