http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57590
--- Comment #11 from janus at gcc dot gnu.org --- (In reply to Mikael Morin from comment #6) > The two above need some adjustements at translation stage, which defeats the > purpose of generating the class container using front-end structures only. > Thus, I'm more in favor of (3): > (3) Don't use gfc_build_class_symbol, or delay it as much as possible until > code generation. Yes, that might indeed be beneficial. I have already thought about this on a few occasions. It would be a larger project for sure, but it could simplify many things. Of course there may also be some pitfalls lurking. I think the cleanest approach would be to keep all the polymorphics as plain BT_CLASS variables (with all the attributes as they are) in the front end and during resolution, and only generate the class containers and vtabs at translation stage.
