- User Since
- Feb 9 2017, 1:53 PM (96 w, 2 d)
Thu, Dec 13
Wed, Dec 12
Some small updates:
Make sure llvm-config reports the c/c++ language standard used.
Fri, Dec 7
Thu, Dec 6
Wed, Dec 5
Is there a particular reason why this and https://reviews.llvm.org/D55259 are separate patches?
I only mentioned -fno-rtti specifically because this is something that llvm-config already knows about. I also don't have knowledge of all the possible flags that might need to be filtered.
Tue, Dec 4
Don't we need to leave -fno-rtti here if LLVM was complied without rtti? Also, rather than filtering out, would it be possible to explicitly add the flags that users need to successfully link/build against this install of LLVM?
Fri, Nov 30
Thu, Nov 29
Wed, Nov 28
Mon, Nov 26
My idea was to stop using llvm-config during the clang (and other sub-project) builds only. I don't have any plans to remove the llvm-config tool from llvm.
Mon, Nov 19
Nov 15 2018
Nov 14 2018
Nov 13 2018
Nov 12 2018
Add a new callback function areFunctionArgsABICompatible for the ArgumentPromotion
pass to use. @echristo I'm still a little confused about what to do with
functionsHaveCompatibleAttributes, should I just leave it as is, or use this new
Nov 9 2018
Some of the clang examples use the add_llvm_loadable_module() macro, so I will need to update those too in a separate patch.
Remove add_llvm_loadable_module() completely.