Re: Transitioning libgomp from C to C++ implementation
Arsen Arsenović <[email protected]>
| Newsgroups | gmane.comp.gcc.devel |
|---|---|
| Organization | BayLibre |
| Message-ID | <[email protected]> |
"Richard Earnshaw (foss)" <[email protected]> writes: > On 08/05/2026 13:23, Alex (Waffl3x) wrote: >> On Fri, May 8, 2026 at 3:51 AM Martin Uecker <[email protected]> wrote: >>> >>> A C library you can usually be used everywhere without much trouble, >>> including various kernel, embedded, and free-standing contexts. So >>> this usually provides more value to users. This may be irrelevant for >>> libgomp though. >>> >>> Martin >> >> C++ supports specifying language linkage with extern "C", the interface >> of a library does not need to match its implementation. Which is also >> what is being proposed here to avoid breaking ABI. >> >> Alex > > That may not be enough if you end up depending on libstdc++ during linking. As mentioned initially, there's no intention to depend on libstdc++. IMO this is a bit dubious but it's not important enough to bikeshed over. -- Arsen Arsenović
signature.asc
(application/pgp-signature, 300 B)
-----BEGIN PGP SIGNATURE----- iKoEARYKAFIWIQT+4rPRE/wAoxYtYGFSwpQwHqLEkwUCaf4fkxsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDIYHGFhcnNlbm92aWNAYmF5bGlicmUuY29tAAoJEFLC lDAeosSTVvIBANeSAujnzYhUuVQkU5Ojrg3UcnWeKs4akQ+YOA9NV7ClAQCdPZ/j rzPP5IXgCjVSh5jvx+bfVY4N6N8u1dC7F1/iBw== =jyDV -----END PGP SIGNATURE-----