RTEMS | Draft: Support for building RTEMS with LLVM toolchains (!1539)

[Sebastian Huber (@sebhub)]

Sebastian Huber started a new discussion on cpukit/libtest/testcovdumpinfo.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161196

 > -void rtems_test_gcov_dump_info( void )
 > +void rtems_test_coverage_dump_info( void )
 >  {
 >    ISR_lock_Context lock_context;
 >  
 > -  _ISR_lock_ISR_disable_and_acquire( &gcov_dump_lock, &lock_context );
 > +  _ISR_lock_ISR_disable_and_acquire( &coverage_dump_lock, &lock_context );
 >  
 > -  if ( !gcov_dump_done ) {
 > +  if ( !coverage_dump_done ) {
 >      Hash_Control result;
 >  
 > -    gcov_dump_done = true;
 > +    coverage_dump_done = true;
 >  
 > +    _IO_Printf( rtems_put_char, NULL, "\n*** BEGIN OF COVERAGE INFO BASE64 ***\n" );

The markers `*** BEGIN OF GCOV INFO BASE64 ***`, `*** END OF GCOV INFO BASE64 ***` and `*** GCOV INFO SHA256 ... ***` are an interface. The test log tools search for them, for example the test output parser of specmake. Please keep them for the GCC data.

The clang dump writes profraw data, not gcda data. A tool cannot decode it as gcda. Please give the clang dump its own markers, for example `*** BEGIN OF PROFRAW INFO BASE64 ***`. A tool then knows the format from the log.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161196
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-1z1843jfnn3ak3uqvhalmyj4t-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20261016/25ad51ed/attachment-0001.htm>