This is the mail archive of the gcc-bugs@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]

[Bug middle-end/50640] [4.7 Regression] FAIL: gfortran.dg/select_type_12.f03 -O (internal compiler error)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50640

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |janus at gcc dot gnu.org,
                   |                            |pault at gcc dot gnu.org

--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-10-07 16:57:08 UTC ---
(In reply to comment #4)
> Or another solution: should the fortran frontend perhaps put all these
> variables not in MAINs scope (where they aren't referenced anyway), but
> rather into file scope?  That last solution would probably be the sanest.

Looks sensible. Janus & Paul, What do you think?

(One can use "pushdecl_top_level (decl)" to push variable decls to file level.)


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