We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·18d ago·5 min read
neither gcc nor clang are compliant with standard c++
TL;DR
GCC and Clang do not comply with the C++ standard regarding function types and language linkage. This oversight leads to issues with function overloading, as the compilers treat distinct types as identical.
✦ Why It Matters
Consider advocating for updates to the C++ standard to address these compliance issues in your projects.
Key Takeaways
- Understand the implications of language linkage in C++ function types.
- Check for potential compilation issues in function pointer overloads.
- Consider updating your code to avoid reliance on GCC and Clang behavior.
- Stay informed about changes to the C++ standard that may affect your code.
How It Works
In C++, function types are defined with a language linkage that determines how they can be called. The standard specifies that different linkages create distinct types, which is crucial for maintaining correct calling conventions across languages.
However, GCC and Clang do not implement this distinction, leading to situations where identical function types are treated as the same, which can cause unexpected behavior.
⚠ The Catch
The lack of language linkage information in GCC and Clang can lead to erroneous compilation failures, particularly when overloading functions that accept function pointers. This oversight violates the one definition rule, which can result in confusing errors for developers.