Thanks for your reply, Sean.
I think the reason users arent complaining about this is because, users
dont link with target libraries.
This is going to be a major cleanup too as there have been a lot of
options defined across all the targets.
A simple find/grep shows you a total of 98 options defined in libraries.
On 8/23/2013 1:41 PM, Sean Silva wrote:
> It is definitely an issue, since the command line options are basically
> globals, which fundamentally goes against LLVM's library-based design.
> -- Sean Silva
> On Fri, Jul 26, 2013 at 7:03 PM, Shankar Easwaran
>> I see a lot of command line options being set in Target backend libraries.
>> The problem with that is if a third party tool links with Target libraries
>> and has a command line option that needs to be processed, the option in the
>> Target libraries will get overridden.
>> $ cd llvm/lib/Target
>> $ grep 'cl::' */*.cpp --> produces lot of such occurences.
>> For example :- libLLVMX86CodeGen.a contains
>> libLLVMX86CodeGen.a:**X86RegisterInfo.cpp.o:**0000000000000080 b
>> I think those command line options would need to be moved to the drivers
>> that are using them, Isnt it ?
>> Am I mistaken ?
>> Shankar Easwaran
>> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted
>> by the Linux Foundation