Yuri
2011-Feb-20 04:28 UTC
[LLVMdev] Why __GNUC__, __GNUC_MINOR__, __GNUC_PATCHLEVEL__ are defined as 4, 2, 1 in clang?
clang isn't GNU C. So why does it define such values and why they are 4,2,1? It also defines __GNUC_STDC_INLINE__=1 for some reason. rev.126022 Yuri
Joerg Sonnenberger
2011-Feb-20 04:55 UTC
[LLVMdev] Why __GNUC__, __GNUC_MINOR__, __GNUC_PATCHLEVEL__ are defined as 4, 2, 1 in clang?
On Sat, Feb 19, 2011 at 08:28:45PM -0800, Yuri wrote:> clang isn't GNU C. So why does it define such values and why they are 4,2,1? > It also defines __GNUC_STDC_INLINE__=1 for some reason.It is mostly compatible with GCC 4.2 and providing the macros makes a lot of code work without modifications. __GNUC_STDC_INLINE__ depends on the choosen level of standard compliance. The (current?) behavior again mimics GCC 4.2.1. Joerg
Apparently Analagous Threads
- [LLVMdev] --enable-shared doesn't build shared library any more
- [LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link
- [LLVMdev] Compiler warnings with gcc-4.7.1
- [LLVMdev] Announcing: LLVM 2.9 Tentative Release Schedule
- [LLVMdev] clang build fails if done in the separate object directory