LuminaSensum/mbed-os

Fork: 0

LuminaSensum / mbed-os

History for mbed-os / tools / toolchains / arm.py

2020-02-21	5f1c777 Browse files » tools: fix SPDX identifiers Martin Kojtal committed on 21 Feb 2020
2020-02-10	03d57b7 Browse files » Add the exception in Mbed OS build tool for Arm Compiler 5 toolchain. Rajkumar Kanagaraj committed on 10 Feb 2020
2020-01-22	6d3782a Browse files » Fix ARM compiler warning for microlib ... - Remove the --library_type=micorlib from c/cxx configuration. Rajkumar Kanagaraj committed on 22 Jan 2020
2020-01-21	Unverified ee1d998 Browse files » Merge pull request #12278 from rajkan01/feature_rename_default_lib ... Rename "default_lib" to "c_lib". Anna Bridge authored on 21 Jan 2020 GitHub committed on 21 Jan 2020
2020-01-21	Unverified 48f90c0 Browse files » Merge pull request #11904 from jamesbeyond/HW_gcov ... TOOLS: enable build greentea test coverage for HW Anna Bridge authored on 21 Jan 2020 GitHub committed on 21 Jan 2020
2020-01-17	8a0fdd2 Browse files » Rename "default_lib" to "c_lib". Rajkumar Kanagaraj committed on 17 Jan 2020
2020-01-15	816516e Browse files » Refactor the code and incorporated the review comment Rajkumar Kanagaraj committed on 15 Jan 2020
2020-01-07	de3c737 Browse files » uARM: Fix deprecate warning printing wrongly for other toolchains. Rajkumar Kanagaraj committed on 7 Jan 2020
2019-12-23	6d081ee Browse files » Fixed the build tools test case failure,incorporated review comments Rajkumar Kanagaraj committed on 23 Dec 2019
2019-12-19	957dca2 Browse files » Enabling small C library option and deprecating uARM toolchain ... - By default, Mbed OS build tools use standard C library for all supported toolchains. It is possible to use smaller C libraries by overriding the "target.default_lib" option with "small". This option is only currently supported for the GCC_ARM toolchain. This override config option is now extended in the build tool for ARM toolchain. - Add configuration option to specify libraries supported for each toolchain per targets. - Move __aeabi_assert function from rtos to retarget code so it’s available for bare metal. - Use 2 memory region model for ARM toolchain scatter file for the following targets: NUCLEO_F207ZG, STM32F411xE, STM32F429xI, NUCLEO_L073RZ, STM32F303xE - Add a warning message in the build tools to deprecate uARM toolchain. - NewLib-Nano C library is not supporting floating-point and printf with %hhd,%hhu,%hhX,%lld,%llu,%llX format specifier so skipping those green tea test cases. Rajkumar Kanagaraj committed on 19 Dec 2019
2019-12-03	d5aef28 Browse files » minimal-printf: Enable using a target configuration parameter Hugues Kamba committed on 3 Dec 2019
2019-11-20	e6fe03f Browse files » TOOLS: fix failed python test Qinghao Shi committed on 20 Nov 2019
2019-10-30	e7964ca Browse files » IOTBTOOL-377: Fix scatter file include path online Mark Edgeworth committed on 30 Oct 2019
2019-07-18	e5a3f97 Browse files » Add TOOLCHAIN_ARMC5 label ... We have some files that are needed for ARMC5 only. Kevin Bracey committed on 18 Jul 2019
2019-05-17	Unverified 9fb4429 Browse files » Merge pull request #10520 from kjbracey-arm/build_tz_heuristic ... Permit non-TrustZone ARMv8 build Anna Bridge authored on 17 May 2019 GitHub committed on 17 May 2019
2019-05-07	fb62ed6 Browse files » Add mbed studio flag during assembly Brian Daniels committed on 7 May 2019
2019-05-03	65e0887 Browse files » Permit non-TrustZone ARMv8 build ... Change the heuristic for selection of CMSE in the tools python, so that a non-TrustZone ARMv8 build can happen. Ideally we would have more direct flagging in the targets, but this refines the heuristic so the necessary behaviour can be easily achieved. * DOMAIN_NS=1 is based purely on the `-NS` suffix on the core name. * Enabling CMSE in the compiler and outputting a secure import library is now enabled when the core doesn't have an `-NS` suffix by either the target label `TFM` being present or the flag `trustzone` being set. This covers the existing ARMv8-M behaviour - TF-M builds have the TFM label, as per its documentation; M2351 secure builds have no explicit flagging, so we ensure that the M2351_NS target has the trustzone flag set, and the out-of-tree secure target inherits that. Kevin Bracey committed on 3 May 2019
2019-04-30	cae568c Browse files » Add Cortex-M33E to cpu conversion table for ARMC6 Alexander Zilberkant committed on 30 Apr 2019
	Unverified 5f2991d Browse files » Handle Cortex-M33E no-fpu flags ... Add compilation "-mfpu=none" flag for Cortex-M33E. Alexander Zilberkant authored on 30 Apr 2019 GitHub committed on 30 Apr 2019
	f58e600 Browse files » Fix armclang fpu detection Oren Cohen committed on 30 Apr 2019
2019-04-23	744e2cc Browse files » Tools: Add "Cortex-M33E" option ... There was a gap in our pattern - we didn't offer M33 with DSP Extension but no floating-point. Kevin Bracey committed on 23 Apr 2019
2019-04-23	56e2d33 Browse files » Correct some CPU selections in tools ... * For ARMC6, core types `Cortex-M4` and `Cortex-M7` did not explicitly add `--fpu=none`, so it defaulted to assuming FPU present. This would cause a compilation error if the target's cmsis.h had `__FPU_PRESENT` defined to 0. * For GCC, `Cortex-M33FE` did not include `+dsp` in the architecture selection. * For ARMC5 and ARMC6, `Cortex-M0+` did not pass `M0plus` to the non-Clang tools. Kevin Bracey committed on 23 Apr 2019
2019-04-05	2a080a0 Browse files » Correct call to add_file_ref Brian Daniels committed on 5 Apr 2019
2019-04-02	f0f133f Browse files » tools: fix the path generated to the sct file ... The sct file path generated in the online compiler is incorrect. Fix that by changing the correct_scatter_shebang API to accept a FileRef object instead and use the path. This change should go with change in online compiler that removes the override for correct_scatter_shebang. Naveen Kaje authored on 6 Mar 2019 Brian Daniels committed on 2 Apr 2019
2019-03-29	992cb26 Browse files » Parse errors and warnings with ARMC6 Jimmy Brisson committed on 29 Mar 2019
2019-03-27	Unverified cfdb72b Browse files » Merge pull request #10182 from lrusinowicz/armc6_assembler_win7_workaround ... Workaround for ARMC6 Windows 7 assembler issue Cruz Monrreal authored on 27 Mar 2019 GitHub committed on 27 Mar 2019
2019-03-23	0f1bd76 Browse files » Add link for ARMC5 warning Brian Daniels committed on 23 Mar 2019
	04e90c2 Browse files » ARMC5 is supported if a target lists ARM as a supported_toolchain Brian Daniels committed on 23 Mar 2019
	6f5a3c3 Browse files » Add functions to enable ARM fallback to ARMC5. ... There are two new functions: get_valid_toolchain_names and find_valid_toolchain. These functions are used to figure out if a fallback is possible and necessary. find_valid_toolchain is expected to be used by the front-end scripts. get_toolchain_name was updated with some different logic and comments. Brian Daniels committed on 23 Mar 2019
2019-03-21	8d8cf1a Browse files » Workaround for ARMC6 Windows 7 assembler issue ... On Windows 7 using --preproc option in ARMC6 assembler doesn't work when -MD option is also specified. Compiler creates incorrect filename for dependency file and compilation files. To workaround this issue, this change returns to using a temporary file and separately calling preprocessor and assembler (as in a case of ARMC5). Leszek Rusinowicz committed on 21 Mar 2019