Displaying 3 results from an estimated 3 matches for "setverboseopt".
2013 Sep 18
2
[LLVMdev] [lld][Options] Sharing common options across flavors
...elp
e) -mllvm
I am also thinking of adding a verbose option that would essentially
control the various verbose outputs that we might want to have. For example:
lld -flavor gnu -target x86_64
--verbose=commandline,trampolines,symbols,reader,writer ....
LinkingContext will have two functions :-
setVerboseOptions(StringRef) -> stores all the verbose options in a vector.
hasVerboseOption(StringRef) -> returns true if the option is present
Thoughts on the above ?
Thanks
Shankar Easwaran
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation
2013 Sep 18
1
[LLVMdev] [lld][Options] Sharing common options across flavors
...bose option that would essentially control the various verbose outputs that we might want to have. For example:
>>
>> lld -flavor gnu -target x86_64 --verbose=commandline,trampolines,symbols,reader,writer ....
>>
>> LinkingContext will have two functions :-
>>
>> setVerboseOptions(StringRef) -> stores all the verbose options in a vector.
>>
>> hasVerboseOption(StringRef) -> returns true if the option is present
>>
>> Thoughts on the above ?
> What do you mean by “verbose”. Is this like DEBUG_WITH_TYPE()?
gnu ld has a verbose option that...
2013 Sep 18
0
[LLVMdev] [lld][Options] Sharing common options across flavors
...nking of adding a verbose option that would essentially control the various verbose outputs that we might want to have. For example:
>
> lld -flavor gnu -target x86_64 --verbose=commandline,trampolines,symbols,reader,writer ....
>
> LinkingContext will have two functions :-
>
> setVerboseOptions(StringRef) -> stores all the verbose options in a vector.
>
> hasVerboseOption(StringRef) -> returns true if the option is present
>
> Thoughts on the above ?
What do you mean by “verbose”. Is this like DEBUG_WITH_TYPE()?
-Nick