Re: RTEMS Executive vs. Kernel

On Fri, Jan 25, 2019, 5:15 PM Chris Johns On 26/1/19 9:43 am, Joel Sherrill wrote: > > We have a full shelf of old reports. A few would be good to have > > mirrored at ftp.rtems.org if DTIC has them. > > Sebastian and I have been discussing using .. > > https://ftp.rtems.or

Re: RTEMS Executive vs. Kernel

On 26/1/19 9:43 am, Joel Sherrill wrote: > We have a full shelf of old reports. A few would be good to have  > mirrored at ftp.rtems.org if DTIC has them. Sebastian and I have been discussing using .. https://ftp.rtems.org/pub/contrib/docs for these type of documents. We

Re: RTEMS Executive vs. Kernel

On Fri, Jan 25, 2019 at 7:03 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 24/01/2019 00:24, Joel Sherrill wrote: > > > > > > On Wed, Jan 23, 2019 at 2:01 AM Sebastian Huber > > > > wrote: > > > > On 23/01/2019 08:11, Chris Joh

Re: [PATCH] rtems-tools/covoar: Wrong coverage computed

On Sat, 26 Jan 2019 at 01:46, Joel Sherrill wrote: > > > On Fri, Jan 25, 2019 at 12:50 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Fri, 25 Jan 2019 at 23:39, Joel Sherrill wrote: >> >>> Sorry for the duplicate email. I didn't use the right email address and >>> the

Re: [PATCH] rtems-tools/covoar: Wrong coverage computed

On Fri, Jan 25, 2019 at 12:50 PM Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: > > > On Fri, 25 Jan 2019 at 23:39, Joel Sherrill wrote: > >> Sorry for the duplicate email. I didn't use the right email address and >> the response did not go to devel@ >> >> On Fri, Jan 25, 2019 at 8:43 AM

Re: [PATCH] rtems-tools/covoar: Wrong coverage computed

On Fri, 25 Jan 2019 at 23:39, Joel Sherrill wrote: > Sorry for the duplicate email. I didn't use the right email address and > the response did not go to devel@ > > On Fri, Jan 25, 2019 at 8:43 AM Jiri Gaisler wrote: > >> Sorry for the noise, but I have a better patch that actually solves the >>

Re: [PATCH] rtems-tools/covoar: Wrong coverage computed

Sorry for the duplicate email. I didn't use the right email address and the response did not go to devel@ On Fri, Jan 25, 2019 at 8:43 AM Jiri Gaisler wrote: > Sorry for the noise, but I have a better patch that actually solves the > root problem. I ran the full testsuite on sis and covoar again

Re: [PATCH] rtems-tools/covoar: Wrong coverage computed

On Fri, Jan 25, 2019 at 8:10 AM Jiri Gaisler wrote: > Here is a final fix that also corrects the coverage computations. The > parsing of the symbol table made all symbols 2 bytes too large, hence the > wrong annotations. I have manually verified the correlation between sis > coverage output and t

Re: GSOC 2019 Aspirant

On Fri, Jan 25, 2019 at 8:44 AM Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: > > > > On Fri, 25 Jan 2019 at 19:50, Ravindra Meena wrote: > >> Hi developers, >> I am new RTEMs. I have setup the RTEMs developement environment and have >> run the Hello World application. Can anyone sugges

Re: Building Ada for RTEMS

On Wed, Jan 23, 2019 at 12:22 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Joel, > > On 22/01/2019 23:04, Joel Sherrill wrote: > > Hi > > > > I put this on hold for the Christmas holidays and wanted to post what > > worked and didn't for me. This is on Centos 7 building

Re: GSOC 2019 Aspirant

On Fri, 25 Jan 2019 at 19:50, Ravindra Meena wrote: > Hi developers, > I am new RTEMs. I have setup the RTEMs developement environment and have > run the Hello World application. Can anyone suggest me the projects > available for GSOC 2019?. > -- > Hello Ravindra, Now that you have completed the

Re: [PATCH] rtems-tools/covoar: Wrong coverage computed

Sorry for the noise, but I have a better patch that actually solves the root problem. I ran the full testsuite on sis and covoar against libscore.a like this: $ sparc-rtems5-ar -rcs sparc-rtems5/c/leon3/cpukit/score/libscore.a sparc-rtems5/c/leon3/cpukit/score/src/*.o $ rtems-test --rtems-bsp=

GSOC 2019 Aspirant

Hi developers, I am new RTEMs. I have setup the RTEMs developement environment and have run the Hello World application. Can anyone suggest me the projects available for GSOC 2019?. -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School

[PATCH] rtems-tools/covoar: Wrong coverage computed

Here is a final fix that also corrects the coverage computations. The parsing of the symbol table made all symbols 2 bytes too large, hence the wrong annotations. I have manually verified the correlation between sis coverage output and the covoar coverage calculations and annotations for a coupl

Re: [PATCH] rtems-tools/covoar: -f switch was not used to select coverage format

On 1/24/19 4:19 PM, Joel Sherrill wrote: > > > On Thu, Jan 24, 2019 at 8:46 AM Jiri Gaisler > wrote: > > > On 1/24/19 2:19 PM, Joel Sherrill wrote: >> >> >> On Thu, Jan 24, 2019, 6:38 AM Jiri Gaisler > wrote: >> >> Small patch t

Re: SIS with coverage support

On Thu, Jan 24, 2019 at 3:04 AM Jiri Gaisler wrote: > > On 1/24/19 9:33 AM, Jiri Gaisler wrote: > > > On 1/24/19 12:45 AM, Joel Sherrill wrote: > > > > On Wed, Jan 23, 2019 at 4:45 PM Chris Johns wrote: > >> On 24/1/19 9:12 am, Jiri Gaisler wrote: >> > After some trial and error, I got covoar to

PowerPC (psim) CPU_FLAGS

Hi, The psim CPU_CFLAGS are: CPU_CFLAGS = -meabi -mcpu=603e -msdata=sysv -fno-common An audit of the CU flags in `hello.exe` [1] shows: 1) -mcall-sysv -meabi -mcpu=603e -msdata=sysv -g -O2 -fno-common 2) -mcpu=603e -g -g -g -O2 -O2 -O2 -fbuilding-libgcc -fno-stack-protector \ -fexception

Re: [PATCH 04/10] user: Add "Obtain the Sources" section

On 24/01/2019 12:17, Chris Johns wrote: On 24/1/19 7:55 pm, Sebastian Huber wrote: --- user/start/index.rst | 1 + user/start/sources.rst | 51 ++ 2 files changed, 52 insertions(+) create mode 100644 user/start/sources.rst diff --git a/u

Re: [PATCH 03/10] user: Rework Prefixes section

On 24/01/2019 12:12, Chris Johns wrote: On 24/1/19 9:49 pm, Sebastian Huber wrote: On 24/01/2019 11:47, Chris Johns wrote: +:file:`/usr/local` on FreeBSD and Linux. + +You have to select a prefix for your RTEMS tool suite installation.  The RTEMS +tool suite consists of a cross tool chain (Binu

Re: RTEMS Executive vs. Kernel

On 24/01/2019 00:24, Joel Sherrill wrote: On Wed, Jan 23, 2019 at 2:01 AM Sebastian Huber > wrote: On 23/01/2019 08:11, Chris Johns wrote: > On 23/1/19 5:50 pm, Sebastian Huber wrote: >> On 22/01/2019 23:42, Chris Johns wrote: >>> On