This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/52265] [OOP] TREE dump confusing with nested SELECT TYPE
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 08 Jun 2012 18:21:36 +0000
- Subject: [Bug fortran/52265] [OOP] TREE dump confusing with nested SELECT TYPE
- Auto-submitted: auto-generated
- References: <bug-52265-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52265
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #2 from janus at gcc dot gnu.org 2012-06-08 18:21:36 UTC ---
(In reply to comment #0)
> Expected: Use different variable names, e.g. via
> gfc_create_var (type, "__tmp_type_t")
I guess the technical problem here is that the temporaries are created already
at resolution stage (in resolve_select_type) on a gfc_symtree level, while
gfc_create_var operates on tree-level (at translation stage).
Do we have any other mechanism for creating temporaries, which could be
employed here? Or do we need to generate a numerically-decorated (or
'randomized') name by hand?