On 11/04/2015 01:45 AM, Jiong Wang wrote: > So as Jim Wilson commented on the bugzilla, instead of "return !strict", > we need to only do the check if strict be true, and only does rejection > which means return FALSE, for all other cases, we need to go through > those normal checks below.
I was just about to submit the same patch myself; my testsuite run finished last night. This testsuite run was with a toolchain configured "--with-arch=armv8-a --with-fpu=neon-fp-armv8 --with-float=hard --with-mode=thumb --enable-languages=c,c++". I see 10 fewer unexpected failures on the gcc testsuite with the patch, and no changes to the other testsuite results. Jim