------- Comment #23 from d at domob dot eu 2008-04-08 13:11 ------- (In reply to comment #22) > > However, I'm not quite sure about some things I did [...] > > I think your patch is in a good enough shape to post it to [EMAIL PROTECTED] > and ask there for comments; this ensures that all gfortraners read it (and not > only three Fortraners) and it makes discussing easier than a in a bugreport.
Ok, sent it in. > I think it is OK for now, but we need to fix it later. I found a test case > which crashes gfortran (ICE, internal compiler error) for nested character > constructors - even without typespec or bounds checks. See PR 35846. I think > this should be fixed together with the rest. I thought about possible solutions when introducing my global variable, namely either to pass them on the argument list down the stack (which is probably what I would do myself), or to abuse the function stack by saving the old value when setting and resetting it on return; while this seems a bit hackish to me, it means probably less changes... In any case, PR 35846 could be a nice other bug for me once this one is done ;) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27997
