Details
- Reviewers
bkramer hubert.reinterpretcast mibintc nsz
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Are we sure this is wise? We know that any future standard C++ type can't be the same as __float128 (without changing the latter) because __float128 mangles the same as 128-bit long double. So by making __float128 the same as _Float128 in C, we're causing the relationship between __float128 and the "corresponding" standard types to differ between C and C++.
I know GCC went in the direction that has this complication. Do we know whether they figured their way out?
This is to make more glibc files compilable with Clang. (@zatrazz)
No, but it's hard to change now. Introducing a GCC incompatible scheme probably does more harm than being compatible with them now...
I know GCC went in the direction that has this complication. Do we know whether they figured their way out?