Re: [PATCH] Ensure __tsan_func_entry call isn't in a loop (PR sanitizer/64265)

2014-12-15 Thread Richard Biener
On Fri, Dec 12, 2014 at 10:33 PM, Jakub Jelinek wrote: > Hi! > > This patch ensures that if successor of entry bb has multiple predecessors, > we emit the __tsan_func_entry call on the edge from entry bb, so it can't > be called inside a loop in the same function. > > Bootstrapped/regtested on x86

[PATCH] Ensure __tsan_func_entry call isn't in a loop (PR sanitizer/64265)

2014-12-12 Thread Jakub Jelinek
Hi! This patch ensures that if successor of entry bb has multiple predecessors, we emit the __tsan_func_entry call on the edge from entry bb, so it can't be called inside a loop in the same function. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2014-12-12 Jakub Jelinek