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

7/10

Technical tradeoffs

  • Transitioning from C to C++ may introduce new dependencies or require more complex build configurations.
  • Ensuring ABI compatibility across different C and C++ codebases is crucial.
  • Maintaining support for diverse operating systems and build environments adds complexity.

All attributes

project
gcc
subsystem
gcc
patch_id
discussion_id
87ik8zzcyc.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
GCC's libgomp, currently C-based, is being transitioned to C++.
proposer
Thomas Schwinge <tschwinge@baylibre.com>
consensus
Proposed
outcome
proposed
sentiment_score
7
technical_tradeoffs
  • Transitioning from C to C++ may introduce new dependencies or require more complex build configurations.
  • Ensuring ABI compatibility across different C and C++ codebases is crucial.
  • Maintaining support for diverse operating systems and build environments adds complexity.
series_id
series_role
standalone
series_parts
[]
tags
  • libgomp
  • OpenMP
  • C++
  • GCC
  • porting
bugzilla_url
date
2026-07-01T00:00:00.000Z

Re: Transitioning libgomp from C to C++ implementation: RTEMS

The libgomp library, which provides OpenMP support in GCC, is being rewritten from C to C++. This transition is expected to affect various targets, including those using RTEMS, Darwin, and Cygwin. “embedded-brains.de” notes that libgomp is enabled for RTEMS targets supporting SMP, and there’s ongoing work sponsored by the European Space Agency for critical systems. “sandoe.co.uk” confirms libgomp support on Darwin, while “10walls@gmail.com” and “lh_mouse@126.com” discuss Cygwin and MinGW considerations, particularly regarding pthread implementations.