[LLVMdev] defining symbols with lld
Shankar Easwaran
shankare at codeaurora.org
Fri Aug 23 15:18:27 PDT 2013
> We only need one reference type, as the resolver only cares that it is
> referenced.
We would need multiple reference types for all the operators that you
need to support, like what Nick mentioned.
It makes it easier to store them in native format too, and can test
reading/writing from core.
>> h) I still need to figure out, what are the ways this symbol can be
>> overridden, if the same symbol is defined in a file, does it override,
>> (Resolver may need to handle it).
>
> It would also be useful to keep source location information about
> expressions so we can give nice diagnostics for things that can only be
> detected by the backend.
For expressions, you mean to say record information, whether it was
defined in the command line
or defined in the linker script ?
If we want to keep source location information, it might be useful to
add this to all the atoms,
as it might be useful to throw information if source code was compiled
with debug information ?
> I'm not completely convinced that DefinedAtom is the correct thing to use
> for this case, as it follows completely different layout rules.
The absolute atom is the only thing that comes to mind which doesnot
have a content/reference list though
as Nick's reply mentioned.
Thanks
Shankar Easwaran
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation
More information about the llvm-dev
mailing list