On Tue, Nov 12, 2013 at 10:07:32AM -0800, Kostya Serebryany wrote: > On Tue, Nov 12, 2013 at 10:04 AM, Michael Meissner > <meiss...@linux.vnet.ibm.com> wrote: > > On Tue, Nov 12, 2013 at 09:43:38AM -0800, Kostya Serebryany wrote: > >> or, alternatively, we can disable libsanitizer on PowerPC if the > >> PowerPC community does not care enough about it being healthy. > > > > I think there should be a global --enable-libsanitizer or whatever option > > that > > would allow people to enable it. It should only be default on x86_64 until > > people are motivated to fix libsantizer on all instances of the platform. > > I don't mind that. > > > > > -- > > Michael Meissner, IBM > > IBM, M/S 2506R, 550 King Street, Littleton, MA 01460, USA > > email: meiss...@linux.vnet.ibm.com, phone: +1 (978) 899-4797 > >
In terms of not being able to reproduce it, I just logged onto the powerpc64 machine on the GCC compile farm (gcc110.fsffrance.org), and I was able to reproduce the bug in about 15 minutes using no special configure options. Here is information about the compile farm: http://gcc.gnu.org/wiki/CompileFarm -- Michael Meissner, IBM IBM, M/S 2506R, 550 King Street, Littleton, MA 01460, USA email: meiss...@linux.vnet.ibm.com, phone: +1 (978) 899-4797
