4 ms·
I'm not very happy to see C++ infecting more and more system software when it STILL IN 2020 doesn't have a stable FFI/ABI. This is going to bite us ALL in the
by bsder 7y ago
I'm not very happy to see C++ infecting more and more system software when it STILL IN 2020 doesn't have a stable FFI/ABI.
This is going to bite us ALL in the future because it will saddle other languages with a useless set of constraints long after C++ gets removed from a project.
- monocasa 7y agoThey don't want to add loadable kernel modules (but instead go pretty strict microkernel), so what would an unstable FFI/ABI really matter?
- jcranmer 7y agoWith the exception of the change to std::string in C++11, which was very, very carefully worked around so that C++11 code can handle C++03-ABI std::string, there have been no changes to the ABI implementation since the Itanium ABI was adopted by gcc almost two decades ago. How is that not a stable ABI?
- flukus 7y ago> How is that not a stable ABI? Because it's an ABI with several severe constraints, especially around the more OO features and templates, plus the solutions introduce even more abstractions: https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B https://community.kde.org/Policies/Binary_Compatibility_Issu...
- pjmlp 7y agoAll ABIs define similar set constraints, specially when the programming languages are a bit more expressive that pseudo-assembly.
- flukus 7y ago> specially when the programming languages are a bit more expressive that pseudo-assembly. Most higher level languages (java, c#, python) handle most of those much better, albeit with a different set of trade offs. Things like adding a private field to a class won't break binary compatibility in a c# apllication. C++ is fairly unique in that it tries to be high level and tries to be low level but the cost is it pushes the complexity of this split personality onto the developers.
- rndgermandude 7y agoThat's not a C++-ABI but a C++-as-compiled-by-gcc-ABI. C++ itself does not define an ABI and different compilers (sometimes even from the same vendors) will use different incompatible ABIs.
- gpderetta 7y agoIt is the linux standard C++ ABI as the defined by the linux standard base. An ABI for low level language is necessarily (OS, architecture) specific, so you can hardly do better than that. There is no ABI that could be usefully defined at the standard level (and even if it somehow were, it would be mostly ignored[1] as compilers wouldn't break compatibility to implement it). [1] I could see the committee standardizing some intermediate portable representation requiring installation time or even JITing in the future though.
- rndgermandude 7y agoIt is not the linux standard C++ ABI, it's just the defacto standard ABI because of gcc's former dominance and clang intimidating the ABI. And I broke things in the past, where I had to recompile stuff, due to different compilers (clang, clang+libc++, gcc in different -std=c++ modes) producing not 100% compatible outputs. You can say it's good enough (most of the time), but it isn't really a standard, unless I am mistaken.
- jcranmer 7y agohttps://uclibc.org/docs/psABI-x86_64.pdf https://uclibc.org/docs/psABI-x86_64.pdf page 106 cares to disagree with: > 9.1 C++ > For the C++ ABI we will use the IA-64 C++ ABI and instantiate it appropriately. The Itanium ABI is the official C++ ABI on Unix systems. (Note that this same document officially documents the C ABI).
- gpderetta 7y agoalthough it might the facto be, at least for AMD64, I wouldn't say it is the official standard ABI of all unix systems. But it is the standard ABI of Linux based systems, at least those that claim to conform to the LSB.
- zelly 7y agoFFI in C++ is never gonna happen with the preprocessor and templates being there. By design of the language it basically won't ever work. You would need to recompile the world unless you're artificially restricting yourself to the equivalent of extern "C". C++20 modules won't make it better either. I don't think Rust, Dart, or Go are any better. In practice it seems C++'s ABI is called "protocol buffers".
- dodobirdlord 7y agoBasically correct, though in Fuchsia it's called FIDL. It's protocol buffers, but not the specific project that Google refers to as "protocol buffers". https://fuchsia.googlesource.com/fuchsia/+/master/docs/development/languages/fidl/tutorial/README.md https://fuchsia.googlesource.com/fuchsia/+/master/docs/devel...
- pjmlp 7y agoWhich is also used by Android.
- pjmlp 7y agoIt works perfectly fine with COM, specially after the COM 2.0 (aka UWP/WinRT) improvements.
- pjmlp 7y agoC++ is moderately safe if one doesn't use it as a C compiler, even standard library does bounds checking across all major compilers, during debug builds and specific compilers switches. There is a stable ABI inside some OSes, moreso than any wannabe C++ replacements. Speaking of which, Rust is a very nice language, but still lacks many productive tooling that systems developers came to expect. If anything this rationale is great input for the Rust community, how to improve the ecosystem.