Rafael Avila de Espindola via llvm-dev
2017-Mar-20 13:16 UTC
[llvm-dev] Please dogfood LLD
Michael Johnson via llvm-dev <llvm-dev at lists.llvm.org> writes:> Hi Rui, > > Are there any plans to support the -defsym command line option?It doesn't look that hard, it was just never requested. What project is using it? Cheers, Rafael
Hi Rafael,> Michael Johnson via llvm-dev <llvm-dev at lists.llvm.org> writes: > >> Hi Rui, >> >> Are there any plans to support the -defsym command line option? > It doesn't look that hard, it was just never requested. What project is > using it?Not sure I understand what the project set is. It's not an uncommon feature for a linker in the embedded world. It's the first problem I discovered when trying to use lld rather than ld e.g. -defsym=__vfprintf=__vfprintf_float_long_long to select a particular implementation of printf. The second problem was failing to parse the .ld script - I can provide it if required. Regards Michael> > Cheers, > Rafael
Rafael Avila de Espindola via llvm-dev
2017-Mar-20 14:17 UTC
[llvm-dev] Please dogfood LLD
Michael Johnson <mpj at rowley.co.uk> writes:> Hi Rafael, >> Michael Johnson via llvm-dev <llvm-dev at lists.llvm.org> writes: >> >>> Hi Rui, >>> >>> Are there any plans to support the -defsym command line option? >> It doesn't look that hard, it was just never requested. What project is >> using it? > Not sure I understand what the project set is. It's not an uncommon > feature for a linker in the embedded world. > > It's the first problem I discovered when trying to use lld rather than > ld e.g. > > -defsym=__vfprintf=__vfprintf_float_long_long > > to select a particular implementation of printf. > > The second problem was failing to parse the .ld script - I can provide > it if required.If you could open bugs for both that would be awesome. Thanks, Rafael