On Fri, Jul 18, 2014 at 9:23 PM, Jakub Jelinek <ja...@redhat.com> wrote: > On Fri, Jul 18, 2014 at 08:42:35PM +0400, Yuri Gribov wrote: >> > Uh. Can you please explain this? That sounds weird. >> >> Sure, this caused maybe-uninitialized warnings with iterator during >> bootstrap. It turned out that *bb_seq_addr (bb) in gsi_start (bb) >> returned something like bb.flags & GIMPLE ? bb.il.gimple.seq : NULL >> and when GCC saw *NULL it rushed to generated uninitialized read. This >> assert silences compiler. > > Why it doesn't trip elsewhere? Do you get the maybe-uninit warning > on asan.c or somewhere else without that?
Just in pass_sanopt::execute in asan.c. -Y
