Date: Sat, 2 Jun 2012 00:03:22 -0400 From: Rich Felker <dalias@...ifal.cx> To: musl@...ts.openwall.com Subject: Re: hm, libc crashes loading libc On Sat, Jun 02, 2012 at 12:18:55AM +0200, aep wrote: > hashtab=0x0 sounds wrong, but how did it become zero? By GCC 4.7 randomly reordering memory accesses with no rhyme or reason. As discussed on IRC, this is GCC bug # 52734 and has nothing to do with musl. Anyone experiencing it and unable to replace the broken GCC can use the -fno-tree-tail-merge option as a workaround. Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.