Ok, I was merely asking, if I need to stop my current fault finding immediately and fix it within the next hours, or if a fix is ok by say beginning of next at latest.
I will finish my current fault finding and then extend your patch. - Andre On Wed, 8 Jan 2025 12:04:15 +0100 Jakub Jelinek <ja...@redhat.com> wrote: > On Wed, Jan 08, 2025 at 11:53:53AM +0100, Andre Vehreschild wrote: > > Well, thinking about it, it smells like a side-effect of the 116669 fix. A > > type getting the recursive marker enforces the generation of the vtype for > > it. I don't see yet, why the iso_c_binding_C_funptr should be marked as > > recursive. I will investigate. How much time do I have? > > To me the other patch (just bumping of MOD_VERSION) is more important than > this one, and this one isn't finished anyway and I'm afraid I don't know > enough about the Fortran class etc. support to finish it myself. > > The ABI has to be fixed by the time GCC 15 is released (so ideally frozen > on/before mid April), but it wouldn't hurt if it is fixed much earlier > (e.g. in Fedora we are building the distro with GCC 15 prerelease in second > half of January, and while it is our risk and we need to be prepared to > rebuild stuff if there are ABI changes and the like, it would be useful if > the *.mod file format didn't change much during stage4 (which is less than a > week away). > > Jakub > -- Andre Vehreschild * Email: vehre ad gmx dot de