This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
FX:
(a) those majority which might need buffering (gfc_error, gfc_warning);Is there a plan for those in the longer term?
Well, the long-term solution is of course to support them. That requires adding buffering+discarding support to the common machinery and to use it then in gfortran. It's on Manuel's to-do list, but he suffers from the generic problem of finding the time to actually do it. Maybe he manages to finish that part by early next year - which might or might not be suitable for GCC 5 inclusion.
Similarly for the support of multiple locations, which would be the next item on his Fortran agenda.
For my side, I was thinking of moving closer to the common infrastructure for reading files, which should help with some issues in scanner.c (last cases of gfc_warning_now_1). That and locking with -fcoarray=lib currently rank high on my gfortran agenda.
The changes to scanner.c also would prepare the way for supporting encodings in strings (like 4_'UTF-8 string' working properly) and for recoding macros such that macro expansion can be properly handled. But all those will surely require quite some extra work - including more work to the common diagnostic machinary as the offset calculation will no longer work in that case. In any case, those are GCC 6+ items.
Tobias
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |