Gcov support in Covoar

Hello, I'm starting this thread for discussions on the gcov support in covoar. Current status is that the code in it (like in GcovData.cc) remained untouched for a long time and it had not been updated after the source tree reorganization which is why it runs into segmentation fault while trying

Re: [rtems-bsp-builder] 2018-07-03 11:41:43: Profile(s): everything

On 04/07/18 02:33, j...@rtems.org wrote: RTEMS Tools Project - RTEMS Kernel BSP Builder, 5 (b762312fae67) Please use the tools from the latest RSB. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchhe

Re: [GSOC - Tracing] Status Update

On 03/07/18 14:50, Vidushi Vashishth wrote: Hi! > Ok, thanks, but why did you remove the RTEMS application? This is the first step. The repository should contain a sample application with a Makefile (or waf or whatever, but no manual steps) to generate a sample trace raw data. I was testing

Epiphany ICE when building mongoose

Hi I think all the build failures from the BSP builder on epiphany are due to a GCC ICE building mongoose. Any thoughts? --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

[PATCH v3] coverage : Add support to run coverage in supported bsp without extra options

Close #3440 --- tester/rt/test.py| 21 ++--- tester/rtems/testing/bsps/leon3-qemu-cov.ini | 1 + 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/tester/rt/test.py b/tester/rt/test.py index 9214ad6..5d25d82 100644 --- a/tester/rt/test.py

Documentation in A4/US letter

Hi As Dannie is wrapping up the Release Notes, I wanted to start a discussion to make sure that all our docs were printable nicely on A4 and US letter. Gedare thinks it is just a matter of margins. Anyone have thoughts on how to produce one set of PDFs that look good on both sizes of paper? Also

BSP Builder Failures

Hi Looks like some BSP variants disappeared and weren't accounted for in rtems-bsp-tiers.ini. + realview_pbx_a9_qemu_smp + altcycv_devkit_smp Then a lot of epiphany failures which must be something else. Should those be dropped from the tiers file? --joel __

Re: GSoC IRC Meeting reschedule: 7/4 to 7/3

Hi! I am sorry for the late update. I might not be able to make it due to a prescheduled doctor's appointment. I will try to get in on the go. I will update the progress on the wiki page as well. I will send a separate progress mail on the mailing list if need be. Thanks On Mon, Jul 2, 2018 at 1

Re: GSoC IRC Meeting reschedule: 7/4 to 7/3

Done, thanks for the feedback! On Tue, Jul 3, 2018 at 2:46 PM, Sebastian Huber wrote: > On 03/07/18 11:01, Amaan Cheval wrote: >> >> - Rebase with master and fix misc. issues that cropped up (commit - >> >> https://github.com/AmaanC/rtems-gsoc18/commit/a28badd8df1904496c27b262ae515d22da544713) >

[PATCH] posix: Check for new prototypes

Update #3342. Update #3343. --- cpukit/configure.ac | 23 +++ cpukit/include/rtems/posix/pthreadimpl.h | 2 +- cpukit/posix/src/mutexgetprioceiling.c | 10 +++--- cpukit/posix/src/psxtransschedparam.c| 2 +- cpukit/posix/src/pthreadsetschedparam

Re: GSoC IRC Meeting reschedule: 7/4 to 7/3

On 03/07/18 11:01, Amaan Cheval wrote: - Rebase with master and fix misc. issues that cropped up (commit - https://github.com/AmaanC/rtems-gsoc18/commit/a28badd8df1904496c27b262ae515d22da544713) This looks good. I would place the    .rtemsstack (NOLOAD) :    { *(SORT(.rtemsstack.*))    }

Re: GSoC IRC Meeting reschedule: 7/4 to 7/3

Hey! Sorry, I totally forgot we meant to reschedule this week's meeting - I have another conflicting commitment at that time. I'll try to pop in for a bit if possible. I'll update the wiki page with this week's work, but here's the update I'd have sent on IRC: - Got basic UART/console driver work