troublesome change
Jason Merrill
jason@cygnus.com
Wed Jun 24 02:08:00 GMT 1998
>>>>> David S Miller <davem@dm.cobaltmicro.com> writes:
> if (! current_function_contains_functions
> && ! decl_function_context (decl)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This really is quite wrong, and the fact that now it affects multiple
> front ends suggests that whatever bug necessitated that workaround
> change should be what is fixed and the workaround removed.
It's not a workaround. It didn't fix any bug. It just seemed to make
sense; you can't defer dealing with a nested function until end-of-file.
But you should feel free to remove it if it's causing problems. That's
what I told the FORTRAN people, but apparently they didn't.
Jason
More information about the Gcc-bugs
mailing list