rtems-5.1 source code test coverage failed

2020-10-22 Thread small...@aliyun.com
hi, all I want test source code coverage in qemu. There are some questions I met. 1. If compiling without -ftest-coverage, the test only produce a percent coverage, no *.gcov file which is important to recognize which lines not execute. 2. If compiling with -ftest-coverage, *.gcno are created in

RTEMS big comment conventions

2020-10-22 Thread Andrew Butterfield
Dear all, In the RTEMS Software Engineering manual, Sec 6.3.2.1 https://docs.rtems.org/branches/master/eng/coding-80cols.html#breaking-long-lines it recommends excessively long comments be broken as follows: /* first line * second line * third, and in this case last line */ In Sec 6.3.5.2 http

Re: rtems-5.1 source code test coverage failed

2020-10-22 Thread Joel Sherrill
On Thu, Oct 22, 2020 at 4:02 AM small...@aliyun.com wrote: > hi, all > I want test source code coverage in qemu. There are some questions I met. > 1. If compiling without -ftest-coverage, the test only produce a percent > coverage, no *.gcov file which is important to recognize which lines not >

Re: RTEMS big comment conventions

2020-10-22 Thread Joel Sherrill
On Thu, Oct 22, 2020 at 6:07 AM Andrew Butterfield < andrew.butterfi...@scss.tcd.ie> wrote: > Dear all, > > In the RTEMS Software Engineering manual, Sec 6.3.2.1 > > https://docs.rtems.org/branches/master/eng/coding-80cols.html#breaking-long-lines > it recommends excessively long comments be broke

Re: RTEMS big comment conventions

2020-10-22 Thread Gedare Bloom
Hi Andrew, On Thu, Oct 22, 2020 at 5:07 AM Andrew Butterfield wrote: > > Dear all, > > In the RTEMS Software Engineering manual, Sec 6.3.2.1 > https://docs.rtems.org/branches/master/eng/coding-80cols.html#breaking-long-lines > it recommends excessively long comments be broken as follows: > > /* f

Re: Fatal exceptions on context-switching for more than two isolated threads

2020-10-22 Thread Sebastian Huber
On 22/10/2020 02:40, Utkarsh Rai wrote: Hello, this thread has gone a bit cold over the last few weeks, due to my engagement in the university tests.  I have provided a debug trace for the issue.  The reason for fatal exceptions is the fact that while iterating over the chain of user extension

[PATCH] score/aarch64: Size saved SP register for ABI

2020-10-22 Thread Kinsey Moore
This ensures that the saved SP register is sized appropriately depending on the chosen ABI and prevents a warning in the libmisc stack checker. --- cpukit/score/cpu/aarch64/include/rtems/score/cpu.h | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/cpukit/score/cpu/aarch64/in

Re: [PATCH] score/aarch64: Size saved SP register for ABI

2020-10-22 Thread Hesham Almatary
On Thu, 22 Oct 2020 at 20:07, Kinsey Moore wrote: > This ensures that the saved SP register is sized appropriately depending > on the chosen ABI and prevents a warning in the libmisc stack checker. > --- > cpukit/score/cpu/aarch64/include/rtems/score/cpu.h | 5 - > 1 file changed, 4 insertio

RE: [PATCH] score/aarch64: Size saved SP register for ABI

2020-10-22 Thread Kinsey Moore
From: Hesham Almatary Sent: Thursday, October 22, 2020 14:51 To: Kinsey Moore Cc: devel@rtems.org Subject: Re: [PATCH] score/aarch64: Size saved SP register for ABI On Thu, 22 Oct 2020 at 20:07, Kinsey Moore mailto:kinsey.mo...@oarcorp.com>> wrote: This ensures that the saved SP register is

Re: RTEMS big comment conventions

2020-10-22 Thread Chris Johns
On 23/10/20 3:13 am, Joel Sherrill wrote: > On Thu, Oct 22, 2020 at 6:07 AM Andrew Butterfield > mailto:andrew.butterfi...@scss.tcd.ie>> > wrote: > > Dear all, > > In the RTEMS Software Engineering manual, Sec 6.3.2.1 > > https://docs.rtems.org/branches/master/eng/coding-80cols.html

RTEMS Presentations at EPICS Collaboration Meeting

2020-10-22 Thread Joel Sherrill
Hi Gedare and Chris presented at the EPICS Collaboration Meeting this week. A news item with links to the presentations is at https://www.rtems.org/node/136. A core theme is that we want RTEMS to be a great foundation for frameworks like EPICS and CFS. Chris did a great job presenting on the pa

Re: Re: rtems-5.1 source code test coverage failed

2020-10-22 Thread small...@aliyun.com
Thanks joel. I google the Couverture-Qemu and find many useful document about rtems test coverage. The conventional approach will compile source codes to create *.gcno files. But the Couverture-Qemu method needn't. In the final report, the Couverture-Qemu method will create an annotated.html f

Re: Re: rtems-5.1 source code test coverage failed

2020-10-22 Thread Joel Sherrill
On Thu, Oct 22, 2020, 8:53 PM small...@aliyun.com wrote: > Thanks joel. > > I google the Couverture-Qemu and find many useful document about rtems > test coverage. > The conventional approach will compile source codes to create *.gcno > files. But the Couverture-Qemu method needn't. > In the fina

Re: Re: rtems-5.1 source code test coverage failed

2020-10-22 Thread Joel Sherrill
Hit send too soon On Thu, Oct 22, 2020, 8:59 PM Joel Sherrill wrote: > > > On Thu, Oct 22, 2020, 8:53 PM small...@aliyun.com > wrote: > >> Thanks joel. >> >> I google the Couverture-Qemu and find many useful document about rtems >> test coverage. >> The conventional approach will compile source

Re: Re: rtems-5.1 source code test coverage failed

2020-10-22 Thread small...@aliyun.com
Thank you once again. Your reply is very very fast. small...@aliyun.com From: Joel Sherrill Date: 2020-10-23 10:03 To: smallphd CC: devel Subject: Re: Re: rtems-5.1 source code test coverage failed Hit send too soon On Thu, Oct 22, 2020, 8:59 PM Joel Sherrill wrote: On Thu, Oct 22, 2020, 8