RTEMS | Emit the build data and the test state as ELF notes (!1561)

Sebastian Huber (@sebhub) gitlab at rtems.org
Thu Nov 5 06:32:55 UTC 2026



Sebastian Huber created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1561

Project:Branches: sebhub/rtems:up/elf-notes to rtems/rtos/rtems:main
Author: Sebastian Huber

## Summary

Issue #4888: Add support for ELF notes

**Problem:** An executable carries no build data which a tool can read without running it. The test programs and the verbose fatal extension print the version and the build label, so each new commit changes the loaded image of every executable.

**Fix:** The start file of each BSP emits a `.note.rtems` section with the version, the build options, the tools, the BSP and the build label. Each test program emits its test state as a note. The linker command files place the section unallocated, so the notes stay out of the loaded image. The test support and the fatal extension no longer print this information.

**Review hints:**

- `<rtems/elfnotes.h>` defines the note format. `<rtems/score/elfnotesbuild.h>` holds the assembler macro of the start files.
- The first commit is an independent fix of the tick conversion check of `libtests/ttest01`.

## Test

`readelf -n` lists the six notes in `hello.exe` of `riscv/rv64imafdc`. The same commits run through the simulator test suites of 13 architectures in the embedded brains CI.

## AI Details
<!-- Make sure you have read our statement at https://www.rtems.org/generative-ai/ -->

### Prompt used

None as a single prompt.  The work was done in an interactive Claude Code session on the RTEMS tree.  Each change was directed and reviewed.

### AI model used

Claude Opus 5.5 (claude-opus-5-5), through Claude Code.

### How AI was used for the contribution

- ( ) Formatting
- ( ) Test creation.
- (x) Code comments.
- ( ) The entire contribution was generated using AI
- ( ) AI code completion such as Copilot in VSCode.

The implementation was produced in that session under my direction, and the commit messages were drafted there.

### Access

I have not used a product which claims copyright in its output, and I have legitimate access to the one I used.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1561
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-7319nnml2c3pxhd6srq3eoubc-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/20261105/72831041/attachment-0001.htm>


More information about the bugs mailing list