On 11/15/2012 03:08 PM, Eric Botcazou wrote: > For a naked call to memcpy? I don't think so, this is a call so there will > be > an abnormal edge at the Tree level. The problem arises only when the > abnormal > edge is created during RTL expansion.
Well, there's a call at the tree level for __sync_synchronize as well. So the question is: why does __s_s ICE but memcmp doesn't? I suppose it's the mere rarity with which HAVE_cmpmemsi is defined, and expansion of gen_cmpmemsi fails. There are plenty of other calls to emit_library_call_value that are not subsequently protected by emit_libcall_block_1, but they are probably sufficiently rare on common platforms that they'd be difficult to trigger. r~
