GNU Fortran IRC meeting planning: When? Agenda?

[FX]

> (a) As Stage 1 ends on October 27, we still have a bit more than a month for medium-size projects. I think implementable and thus worth to discuss (or get status updates) are
> - REAL(16) support for __float128 systems

I'll try to be there for the meeting.

> - CPP: Add some target support, e.g. Kai's patch for PR 42954

That would be really good!

> (c) Larger tasks:
> - Array descriptor update: Something to get ready for 4.7; needs some work - so far only Paul was brave and worked on it. Besides the basic support, we need to think about which fields should be included - includes thinking about CLASS(*) and about DT kind/len parameters
> - Memory tracking:* Diagnostics - but also correctness (let DEALLOCATE fail for nonallocated memory like named TARGETs)
> - FINAL:* Daniel wants to work on this ...
> - OOP - arrays and unlimited polymorphism
> - Coarrays - going truly multi-image


> - IEEE - most hated item, least wanted item - but feature most other compilers have?

OK, probably it's not good to announce that in advance, but... I would like to work on this for 4.7, if someone can help me with reworking the front-end support for intrinsic modules (which is currently quite ad hoc, and not generic as code in intrinsic.c/simplify.c/iresolve.c/check.c).


> - Submodules & speedup of module reading [revamp of the format?]

One improvement (maybe already present?) is that, for loading modules from the same file, we should keep it in memory and not read it back from disk (with a maximum memory used size, probably).

> - libcpp - going away from -traditional-cpp and getting more TARGET_*_CPP_BUILTINs to work (cf. PR 42954 above)

Yes! and supporting non-ASCII input as well.


FX