search for: vlai

Has anybody able to compile glibc with newer version of clang/llvm. If its not possible is there any patch to fix this problem. Thanks Wajih -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140918/59904126/attachment.html>

...res are > welcome. Patches accepted! > > The Linux Kernel has some issues with being compiled with Clang; these > are issues which the LLVMLinux project is attempting to fix in the Linux > Kernel code base and pushed upstream: > > * The use of variable length arrays in structs (VLAIS) > * Kbuild support for Clang (currently Kbuild is gcc specific) > * Use of explicit register variables > * Extra __refdata annotations needed to overcome segment reference errors > * EXPORT_SYMBOL of inline functions > > However, there are some things in Clang/LLVM which also ne...

...ns to support other architectures are welcome. Patches accepted! The Linux Kernel has some issues with being compiled with Clang; these are issues which the LLVMLinux project is attempting to fix in the Linux Kernel code base and pushed upstream: * The use of variable length arrays in structs (VLAIS) * Kbuild support for Clang (currently Kbuild is gcc specific) * Use of explicit register variables * Extra __refdata annotations needed to overcome segment reference errors * EXPORT_SYMBOL of inline functions However, there are some things in Clang/LLVM which also need to be addressed in order...

...ve? 3. Deprecation =========== Legacy sucks, we all know that. GCC takes the view that they can't remove *any* legacy, which is exactly the opposite of what we do. I don't see a problem here. As LLVM becomes more mainstream, code that uses legacy extensions (such as nested functions and VLAIS) will be left out by at least one of the compilers, and if the user wants to be compiler agnostic, s(he) will *have* to use the common denominator, which has to be *at least* the language standard. But this also means that if we start adding bells and whistles, we may never get it widely used if...

...bler path to the ARM assembler - Making sure it uses the right external assembler(Android EABI GNU assembler) 7. Fixing the subsequent build errors - RCU header had some static code check which had to be disabled since in clang case alone it was an error not in gcc - VLAIS in various kernel components had to be changed to non-VLAIS to work with clang 8. Updating VLAIS to non-VLAIS in various kernel components - Disk encryption - USB Gadget/Function Filesystem - CRC32 - Netfilter 9. Fixing linker errors for duplicate exception sect...