Re: Transitioning libgomp from C to C++ implementation: RTEMS
Project / Subsystem
gcc / gcc
Date
2026-07-01
Proposer
Thomas Schwinge <tschwinge@baylibre.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Rewriting libgomp in C++ may improve maintainability and introduce modern language features but could introduce new challenges or regressions.
- • Ensuring compatibility with embedded systems like RTEMS requires careful testing and validation.
- • The transition to C++ might impact ongoing efforts related to using libgomp in critical systems, necessitating careful management.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- 878q7uuy9w.fsf@euler.schwinge.ddns.net
- source_type
- public_inbox
- title
- Re: Transitioning libgomp from C to C++ implementation: RTEMS
- headline
- Transitioning libgomp from C to C++ implementation: RTEMS
- tldr
- Discussion on the ongoing effort to rewrite libgomp in C++ and its implications for RTEMS support.
- proposer
- Thomas Schwinge <tschwinge@baylibre.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Rewriting libgomp in C++ may improve maintainability and introduce modern language features but could introduce new challenges or regressions.
- • Ensuring compatibility with embedded systems like RTEMS requires careful testing and validation.
- • The transition to C++ might impact ongoing efforts related to using libgomp in critical systems, necessitating careful management.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • gcc
- • libgomp
- • OpenMP
- • RTEMS
- • C++
- bugzilla_url
- —
- date
- 2026-07-01T00:00:00.000Z
Re: Transitioning libgomp from C to C++ implementation: RTEMS
Thomas Schwinge provides an update on the effort to transition libgomp from a C to a C++ implementation, seeking confirmation on RTEMS support. Sebastian Huber confirms that libgomp is enabled by default for RTEMS targets supporting SMP and is actively used. Huber also notes that the switch to C++ might cause ‘headaches’ for ongoing ESA-sponsored critical systems work, but expresses confidence that it should not be a concern for the RTEMS implementation itself.