search for: typefirstinsection

Thanks for the reply Nick. I will use the Writer::addFiles functionality. Do you want to move the SimpleFile class to lld/Core ? It might be useful for other types of object files too(like for ELF here). How does typeFirstInSection/typeLastinSection know that the addresses that need to be used for those symbols are the symbol values for the section start / section end ? I didnt see references to typeFirstInSection/typeLastInSection in the MachO part of lld too, any pointers to how you are doing that will be helpful. If...

...ols), the writer returns a File object akin to a static library. That it, it provides no initial atoms, but can provide atoms as a last resort (so an .o files would override it). The WriterMachO already uses the addFiles() method to add CRuntime symbols. 2) DefinedAtom::ContentType already has typeFirstInSection and typeLastInSection. These are intended to be used for the content type of the atoms which represent the magic symbols for the start and end of a section. The key here is that the Pass (not written yet) which sorts atoms, knows to sort these atoms to the start or end of their respective section...

Hi Nick, We have few symbols like __bss_start, __bss_end, which are Undefined symbols in the code. I want a way in the Reader to create specific atoms before the linker bootstraps. I didnt find a way to do that with the existing interfaces. The way it needs to work is as below :- 1) ReaderELF creates Absolute symbols (for __bss_start, __bss_end etc) 2) ReaderELF reads each file and adds

...he writer returns a File object akin to a static library. That it, it provides no initial atoms, but can provide atoms as a last resort (so an .o files would override it). The WriterMachO already uses the addFiles() method to add CRuntime symbols. > > 2) DefinedAtom::ContentType already has typeFirstInSection and typeLastInSection. These are intended to be used for the content type of the atoms which represent the magic symbols for the start and end of a section. The key here is that the Pass (not written yet) which sorts atoms, knows to sort these atoms to the start or end of their respective section...

+llvmdev On 10/01/12 21:06, Sid Manning wrote: > > I committed a patch to update the ReaderELF.cpp that, in light of some > recent changes in the writer, may need another update. WriterELF is > looking for atoms of type, typeFirstInSection (STT_SECTION) but the > reader isn't classifying those yet. > > I know there has been some discussion about discarding symbols of type > STT_SECTION but I don't think that is safe. This section would never > make it into the final executable: > >> .section .monkey, &...

...org Qualcomm Innovation Center, Inc is a member of the Code Aurora Forum On 10/01/12 21:06, Sid Manning wrote: > > I committed a patch to update the ReaderELF.cpp that, in light of some > recent changes in the writer, may need another update. WriterELF is > looking for atoms of type, typeFirstInSection (STT_SECTION) but the > reader isn't classifying those yet. > > I know there has been some discussion about discarding symbols of type > STT_SECTION but I don't think that is safe. This section would never > make it into the final executable: > >> .section .monkey,...