This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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]

Re: Gfortran internal tree structure


Daniel Kraft wrote:
Another thing would be to create a gfc_expr structure next to the gfc_code one; I think those two should be the most important ones, but maybe also gfc_symbol might be of interest? (Variables, derived-types, procedures are all symbols, right?)

(Loosely related: Regarding the trans*.c generated code, arrays are also of interest -- in this case even for users, which want to mix Fortran with, e.g., C/C++. See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34528 (and also related PR 34742 and PR 35276). However, for users, the true solutions is the enhanced C interoperability TR (technical report) which is currently developed.)


Incidentally, dump-parse-tree.c could do with updating and, I have no
doubt, could always stand some improvement in the format.
Just one thing: How can I even use those dump-functions?
-fdump-parse-tree


Tobias



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]