== Progress == 2 days off (4/10)
* Infrastructure/validation: (3/10) further checking of cross-testing results stability on aarch64-linux - found a workaround for a timestamp problem (_Pragma3 testcase) - looked at c11-atomic-exec-5 whose execution time ranges between 1s and 1h :-) - forcing make check to -j8 seems to work well, will work on a nicer improvement
* reported and briefly looked at failure in a new libstdc++ test (directory_iterator) on armv5t
* Misc (conf calls, meetings, emails, ....) (2/10)
* Internal (1/10) - GNU linker patch review
On Oct 2, 2015, at 8:38 AM, Christophe Lyon christophe.lyon@linaro.org wrote:
== Progress == 2 days off (4/10)
- Infrastructure/validation: (3/10)
further checking of cross-testing results stability on aarch64-linux
- found a workaround for a timestamp problem (_Pragma3 testcase)
contrib/gcc_update --touch is the best way to fix the above issue.
- looked at c11-atomic-exec-5 whose execution time ranges between 1s
and 1h :-)
I even seeing that on thunderx.
- forcing make check to -j8 seems to work well, will work on a nicer
improvement
- reported and briefly looked at failure in a new libstdc++ test
(directory_iterator) on armv5t
Misc (conf calls, meetings, emails, ....) (2/10)
Internal (1/10)
- GNU linker patch review
linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
On 2 October 2015 at 18:04, Pinski, Andrew Andrew.Pinski@caviumnetworks.com wrote:
On Oct 2, 2015, at 8:38 AM, Christophe Lyon christophe.lyon@linaro.org wrote:
== Progress == 2 days off (4/10)
- Infrastructure/validation: (3/10)
further checking of cross-testing results stability on aarch64-linux
- found a workaround for a timestamp problem (_Pragma3 testcase)
contrib/gcc_update --touch is the best way to fix the above issue.
Yes, that's what I added to abe.
- looked at c11-atomic-exec-5 whose execution time ranges between 1s
and 1h :-)
I even seeing that on thunderx.
Thanks for the confirmation, I saw your comment on bugzilla.
I understood you thought it was a HW problem with your platform. Since we see it on different HW, it could mean there is an implementation problem in libatomic?
- forcing make check to -j8 seems to work well, will work on a nicer
improvement
- reported and briefly looked at failure in a new libstdc++ test
(directory_iterator) on armv5t
Misc (conf calls, meetings, emails, ....) (2/10)
Internal (1/10)
- GNU linker patch review
linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
linaro-toolchain@lists.linaro.org