search for: verifyarch

...ld call the varargs function in the LinkingContext and raise an error if the input is not suitable with the current link mode. > Yes. We need a way to error out if there is an architecture mismatch. But there are some interesting scenarios we need to support. Ok. will create a varArg function (verifyArch ?) I am trying to see if variadic functions would be another alternative too. > * If linking with a static library, you may not know until you actually need to load one of the members if the architecture is wrong, and it may not be an error if the architecture is wrong, but nothing is loaded....

...an error if the input is not suitable with the current link mode. >>>> >>> Yes. We need a way to error out if there is an architecture mismatch. >>> But there are some interesting scenarios we need to support. >>> >> Ok. will create a varArg function (verifyArch ?) >> >> I am trying to see if variadic functions would be another alternative too. >> >> * If linking with a static library, you may not know until you actually >>> need to load one of the members if the architecture is wrong, and it may >>> not be an err...

On Oct 4, 2013, at 8:50 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > It is needed that lld verifies the input to the linker. > > For example : a x86 ELF file can be given to lld when the target is x86_64. Similiarly with other flavors. > > I was thinking to have a varargs function in the LinkingContext that would be overridden by each of the LinkingContexts to

Hi, It is needed that lld verifies the input to the linker. For example : a x86 ELF file can be given to lld when the target is x86_64. Similiarly with other flavors. I was thinking to have a varargs function in the LinkingContext that would be overridden by each of the LinkingContexts to verify files after being read. The reader would call the varargs function in the LinkingContext and