Re: [tools] tester: Normalize JSON and YAML reports

On 29/06/2022 08:40, Sebastian Huber wrote: Report the same data in JSON and YAML reports. Do not report redundant information. Update 4671. This patch changes the JSON reports. Are there already consumers for the JSON reports so that we have to be backward compatible? -- embedded brains G

[tools] tester: Normalize JSON and YAML reports

Report the same data in JSON and YAML reports. Do not report redundant information. Update 4671. --- tester/rt/test.py | 191 ++ 1 file changed, 40 insertions(+), 151 deletions(-) diff --git a/tester/rt/test.py b/tester/rt/test.py index 113936c..5b868

[PATCH 08/12] gcov: Add functions to dump the gcov information

Update #4670. --- cpukit/include/rtems/score/io.h | 4 + cpukit/include/rtems/test-info.h| 6 ++ cpukit/libtest/testgcovdumpinfo.c | 66 ++ cpukit/score/src/iogcovdumpinfo.c | 101 + cpukit/score/src/iogcovdumpinfobase64.c | 111

[PATCH 06/12] build: Allow separate optimization flags

Allow separate optimization flags for libraries and tests. For example, the libraries may be built without optimization if coverage instrumentation is enabled, however, the tests may still use optimization. Update #4670. --- spec/build/bsps/bspopts.yml | 6 ++ spec/build/bsps/optcfl

[PATCH 09/12] gcov: Add wrapper to dump the gcov info

Update #4670. --- cpukit/libtest/testgcovbspreset.c | 54 +++ cpukit/libtest/testgcovcpufatalhalt.c | 54 +++ spec/build/cpukit/librtemstest.yml| 2 + 3 files changed, 110 insertions(+) create mode 100644 cpukit/libtest/testgcovbspreset.c

[PATCH 12/12] libtests/crypt01: Avoid stack overflows

The SHA512 functions may use huge amounts of stack space if compiled without optimization. --- testsuites/libtests/crypt01/init.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/testsuites/libtests/crypt01/init.c b/testsuites/libtests/crypt01/init.c index 0944aa60f7..26ba

[PATCH 10/12] build: Add RTEMS_COVERAGE option

Update #4670. --- spec/build/bsps/optcflags.yml | 2 +- spec/build/cpukit/cpuopts.yml | 10 + spec/build/cpukit/grp.yml | 2 ++ spec/build/cpukit/optcoverage.yml | 16 ++ spec/build/cpukit/optcoveragecflags.yml| 20 +

[PATCH 11/12] samples/minimum: Prevent a stack overflow

Prevent a stack overflow if RTEMS_COVERAGE is enabled. --- testsuites/samples/minimum/init.c | 5 + 1 file changed, 5 insertions(+) diff --git a/testsuites/samples/minimum/init.c b/testsuites/samples/minimum/init.c index c988d6d750..4238c47659 100644 --- a/testsuites/samples/minimum/init.c +

[PATCH 05/12] build: Add cppflags, cflags, cxxflags to groups

Propagate the group defined cppflags, cflags, and cxxflags from parent groups to child items through the build item context. Update #4670. --- spec/build/bsps/aarch64/a53/grp.yml | 3 +++ spec/build/bsps/aarch64/a72/grp.yml | 3 +++ spec/build/bsps/aarch64/grp.ym

[PATCH 00/12] Support gcov instrumentation

This patch set adds support to build the RTEMS libraries with gcov instrumentation to get code and branch coverage. There are some improvements necessary in the build system to support different compiler flags for libraries and tests. In general, code coverage is enabled by the new RTEMS_COVERAGE

[PATCH 01/12] build: Add more flags to BuildItemContext

Add cppflags, cflags, and cxxflags to BuildItemContext. This allows to propagate the flags from parent items to child items. Update #4670. --- wscript | 93 +++-- 1 file changed, 70 insertions(+), 23 deletions(-) diff --git a/wscript b/wscript

[PATCH 02/12] build: Move BSP_INCLUDES split

The goal is to let the build items define as much as possible. --- spec/build/bsps/optincludes.yml | 1 + wscript | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/spec/build/bsps/optincludes.yml b/spec/build/bsps/optincludes.yml index 0b4a71031c..ea57fe

[PATCH 04/12] build: Improve value substitution

The waf build system uses lists for tool flags. The build items may use variable substitution. Add the ability to use the variable substitution in lists. For example: MORE_FLAGS = ['-more', '-flags'] flags: - -some-flag - ${MORE_FLAGS} Before this change, the ${MORE_FLAGS} was substituted to

[PATCH 07/12] gcov: Add fork(), etc. gcov wrappers

The compiler wraps fork(), etc. system calls if coverage generation is enabled. These functions must be provided by the system. For RTEMS, they just return an error status. Update #4670. --- cpukit/libcsupport/src/gcovfork.c | 94 +++ spec/build/cpukit/librtemscpu.yml

[PATCH 03/12] build: Fix identifier pattern

Allow upper case characters in identifiers. Update #4670. --- wscript | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wscript b/wscript index 38910f2816..731d1402ff 100755 --- a/wscript +++ b/wscript @@ -112,7 +112,7 @@ class EnvWrapper(object): class Template(string.Temp

Re: Congratulations to Two Core Developers

Congratulations, Gedare and Hesham! I had the honor and privilege of working with both of you, and your knowledge and passion have been a true inspiration to me. Best, Vijay On Tue, Jun 28, 2022 at 8:23 AM Joel Sherrill wrote: > > Hi > > I'd like to congratulate two RTEMS core developers on rec

Congratulations to Two Core Developers

Hi I'd like to congratulate two RTEMS core developers on recent significant achievements. (1) Gedare Bloom was granted tenure at the University of Colorado at Colorado Springs. (2) Hesham Almatary has passed his Ph.D. viva/orals and is nearing graduation. These are both major life events and th

[PATCH] bsps/xilinx-zynq: Init debug console only once

Initialize the debug console only once during early system initialization. --- bsps/arm/xilinx-zynq/console/debug-console.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/bsps/arm/xilinx-zynq/console/debug-console.c b/bsps/arm/xilinx-zynq/console/debug-console.c index 0e9

Integrating the Formal Methods part of Qualification

Dear RTEMS Developers, While the validation tests from the RTEMS pre-qualification activity are now merged into the RTEMS master, the work done in investigating and deploying formal methods techniques is not yet merged. The activity had two main phases: a planning phase (Nov 2018-Oct 2019) that