search for: atomsections

...s representing non SHF_ALLOC atoms in the Atom model. We currently don't have a type for this, and DefinedAtom.cpp makes assumptions about the permissions of an Atom based on their type, so it's hard to use an existing type. The next problem is in the ELF writer. It currently cannot handle AtomSections that are not in a segment as file offsets and addresses are never set. This means that assignOffsets is not called, and that the atoms within are never added to the _atomToAddressMap. However, we can't just add them to that map with their virtual address, as they don't have a virtual addres...

...y). The advantage of this approach would be that Garbage collection would remove all the unneeded references automatically when the definedatom is removed. I think Nick also mentioned about a similiar way a while back. > The next problem is in the ELF writer. It currently cannot handle > AtomSections that are not in a segment as file offsets and addresses are > never set. This means that assignOffsets is not called, and that the atoms > within are never added to the _atomToAddressMap. However, we can't just add > them to that map with their virtual address, as they don't have a...

A bit off topic: ARM Group relocations define a logical set of consequent instructions to be relocated to form one single address. For such relocations a 1 to 1 relation is also met, so no need of special processing in applyRelocation. Concerning native format: it also introduced unneeded code complexity to me when I wanted to set calculated relocation addend back into the Reference object in the

...atoms in the Atom model. We > currently don't have a type for this, and DefinedAtom.cpp makes assumptions > about the permissions of an Atom based on their type, so it's hard to use > an existing type. > > The next problem is in the ELF writer. It currently cannot handle > AtomSections that are not in a segment as file offsets and addresses are > never set. This means that assignOffsets is not called, and that the atoms > within are never added to the _atomToAddressMap. However, we can't just add > them to that map with their virtual address, as they don't have a...

...; removed. > > I think Nick also mentioned about a similiar way a while back. You can't just parse it by byte ranges and pull some out. You would actually need to parse the DWARF and rewrite it. > > > The next problem is in the ELF writer. It currently cannot handle >> AtomSections that are not in a segment as file offsets and addresses are >> never set. This means that assignOffsets is not called, and that the atoms >> within are never added to the _atomToAddressMap. However, we can't just >> add >> them to that map with their virtual address, as...

Hi, The round trip passes just tries to load a *complete* object file in YAML/Native format back. The internal state should be the complete object file in native/yaml format. If some state is not recorded and that is really needed in the writer, we should add that to the Atom model. Shankar Easwaran On 2/9/2015 1:29 PM, Rui Ueyama wrote: > I want to bring this again because I think

Hi, I need an advice on implementation of a very specific kind of relocations used by MIPS N64 ABI. As usual the main problem is how to pass target specific data over Native/YAML conversion barrier. In this ABI relocation record r_info field in fact consists of five subfields: * r_sym - symbol index * r_ssym - special symbol * r_type3 - third relocation type * r_type2 - second relocation type