http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-08-29 10:48:39 UTC --- But what would be a good limit for the parameter? On some targets some people have managed to trigger it even with the parameter 20 which has been the default for a while, but on other code/targets even a few hundred is fine. As I wrote on gcc-patches I think, what we could do is just drop the expression on the floor instead of asserting if it is >= 64KB, or we could stick it into a DW_TAG_dwarf_procedure (though, I think >= 64KB location expressions ought to be rarely useful).
