http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51522
--- Comment #7 from Janne Blomqvist <jb at gcc dot gnu.org> 2012-02-03 22:36:13 UTC --- (In reply to comment #6) > If I try the example of comment 4 with the line break before "&" undone and > using the newest 4.7 trunk (clean build), I see in valgrind: > > ==14154== Invalid read of size 4 > ==14154== at 0x52D345: resolve_symbol (resolve.c:10559) > ==14154== by 0x54131F: do_traverse_symtree (symbol.c:3385) > ==14154== by 0x530093: resolve_types (resolve.c:13859) > ==14154== by 0x5243DB: gfc_resolve (resolve.c:13959) Yes, I saw the same thing. But, as I didn't see any relation between resolve.c:10559 and the r183681 patch, I assumed this was something which was present before and didn't investigate further. Also, looking at the r183681 patch itself at http://gcc.gnu.org/ml/fortran/2012-01/msg00255.html, I find it difficult to see how it can cause any problems (*knocking on wood*).
