Testing a GCC patch for ARM
Hello, I have a patch for ARM that I want to test and I'm not sure what's the procedure of testing in Linaro nor to where it should be committed. (GCC trunk? it's currently under bug fixes mode only). I appreciate help with that. Thanks, Revital ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] January 4th - 9th
== GCC == Pulled down new commits from upstream GCC. My test build failed due to a new cross-build configure problem. Found the problem in GCC Bugzilla, and rolled back to the revision before the problem one. Those sources built ok, so I've pushed the changes to Linaro GCC 4.6 branch. It it now updated to 31st December. Discussed cross-build problems with Alexander Sack on IRC. Merged, tested and pushed all the outstanding Launchpad merge requests into GCC 4.4 and 4.5. Merged, tested and pushed all new CS SG++ patches into Linaro GCC 4.5. Merged, tested and pushed GCC 4.5.2 from upstream into Linaro 4.5. Spun releases for both Linaro GCC 4.4 and 4.5. Brought the Linaro patch tracker up to date. == Other == Catch up with lots of email following my two week holiday. Updated some of the CS patch tracker. Travel to Dallas for the Linaro sprint. --- Next week (10th-14th Jan): Linaro sprint in Dallas Following week (17th-21st Jan): CS annual meeting in Phoenix ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] January 3rd-9th
== Linaro GCC == * Continued hacking on (cleaning up, testing) NEON element/structure load/store (etc.) intrinsics-improvement patch. This now passes all the auto-generated neon.exp tests (admittedly only a very weak test for correctness), and the small number of hand-written tests I threw at it, so hopefully we can declare victory soon. (This patch provides huge improvements to generated code for the "fancy" NEON load/store intrinsics and vtbl/vtbx lookup instructions, and hopefully also provides part of the solution for allowing the vectorizer to use the fancy loads/stores also.) == Misc == * Public holiday Monday. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Jan.3 -- Jan.9
== Last week == * Some discussion about libffi variadic function support. The current proposed design is an additional API function to prepare a new call interface (CIF) structure with the argument number settings for each variadic call site. This IMHO, is slightly less flexible that doing a call-time placement style interface, but should be faster and easier to implement. * Collecting a few cases of ARM/Thumb-2 integration in the GCC ARM backend. * Prepared and traveled to Dallas for the Linaro sprint. == This week == * The Linaro sprint. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Jan. 3 -- Jan. 9
== Last Week == * Worked to improve libunwind test suite results using new ARM-specific unwinding. Managed to reduce the number of failures, but some tests still fail. * Tested latest ltrace upstream tree and determined that It Is Good. Hopefully, this marks the cusp of a new release that includes my work. == This Week == * Finish up work with libunwind. Update wiki brain dump. -- Zach Welch CodeSourcery zwe...@codesourcery.com (650) 331-3385 x743 ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
