search for: virtualaddress

...cs lib. It is weird that if I don't use the llvm-lib but directly "lld-link /NODEFAULTLIB /ENTRY:main main.obj intrinsics.obj", the below example can pass link. Please advise what's wrong in this example. $ cat main.c typedef struct { struct MAP_LIST { unsigned long long VirtualAddress; void *MapCookie; } MapList[100]; } SNP_DRIVER; SNP_DRIVER snp_instance; int main() { SNP_DRIVER *Snp; Snp = &snp_instance; for (int Index = 0; Index < 100; Index++) { Snp->MapList[Index].VirtualAddress = 0; Snp->MapList[Index].MapCookie = 0; }...

...main main.obj intrinsics.obj”, the below example can pass link. >> Please advise what’s wrong in this example. >> >> >> >> >> >> $ cat main.c >> >> typedef struct { >> >> struct MAP_LIST { >> >> unsigned long long VirtualAddress; >> >> void *MapCookie; >> >> } MapList[100]; >> >> } SNP_DRIVER; >> >> SNP_DRIVER snp_instance; >> >> int main() >> >> { >> >> SNP_DRIVER *Snp; >> >> Snp = &snp_instance; &gt...

...work in. What do you think won’t work. If its a non zero sized atom, like for example :- definedatoms: - name : fna size : 4 ... ... definedatoms: - name: fnb size: 4 If I alias the atom, and add a layoutBefore from *fna* to *fnb*, fnb is going to have a seperate virtualaddress from fna. But you essentially wanted fna, fnb to have the same virtual address right ? Am I misreading something that you said ? > > >> I was thinking to model this for ELF for the below functionalities :- >> >> a) __wrap >> >> For example : --wrap fn >>...

On 9/13/2013 8:51 PM, Nick Kledzik wrote: >> If I alias the atom, and add a layoutBefore from fna to fnb, fnb is going to have a seperate virtualaddress from fna. > This sounds like you mean “alias” to mean take one implementation and override another implementation (that has a different name) Yes. I think ELF could treat it as a Layout-Before reference too. This way Darwin can share the same functionality. Thanks for the explanations, Nick....

...zero sized atom, like for example :- > > definedatoms: > - name : fna > size : 4 > ... > ... > > definedatoms: > - name: fnb > size: 4 > > If I alias the atom, and add a layoutBefore from fna to fnb, fnb is going to have a seperate virtualaddress from fna. This sounds like you mean “alias” to mean take one implementation and override another implementation (that has a different name). -Nick > > But you essentially wanted fna, fnb to have the same virtual address right ? > > Am I misreading something that you said ? >>...

...and their bounds, check if the relocation lands within a section o Subtract the section address from the relocation address Since getAddress isn’t in RelocationRef at the moment, this is going to have to be getAddress for MachO and COFF. COFFObjectFile::getRelocationOffset returns R->VirtualAddress, so inside here I’m going to have to find the section it belongs to, add it to the result so it can later be subtracted off by llvm-objdump MachOObjectFile::getRelocationOffset also returns getAnyRelocationAddress so I’ll have to also find its containing section and add this in just so llvm-obj...

On Sep 13, 2013, at 3:35 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > This would work only if an alias is another name for the same symbol(weak symbols). I don’t know what that means. Can you clarify? > > If what is being aliased is another function definition, which is a non zero sized atom, aliasing will not work. That is the exact scenario I think it *will* work

Hi, Thanks a lot for your answer. It seems lld is still the best solution, even if it does not work "right out of the box" for us today. We already have a solution for the "objcopy" part (added the required output format to llvm-objdump). The ScriptLayout class seems to be empty for now (on the master branch at least), but we do not need linker scripts today. All that is

Hi Nick, This would work only if an alias is another name for the same symbol(weak symbols). If what is being aliased is another function definition, which is a non zero sized atom, aliasing will not work. I was thinking to model this for ELF for the below functionalities :- a) __wrap For example : --wrap fn What I plan to do here is, create a undefined function fn atom create a defined

.... msvcrt: Fix ungetc on files with empty buffer. msvcrt: Support NULL buffer in setvbuf. msvcrt: Use file->_flag to check if file buffering is enabled. msvcrt: Don't touch _bufsiz value while initializing FILE structure. Sebastian Lackner (23): kernel32: Update VirtualAddress of resource section in write_raw_resources. msvcr110: Fix typo in exported symbol _set_SSE2_enable. user32: Avoid race-condition when unloading module while hook is still active. kernel32: Raise DBG_PRINTEXCEPTION_C exception in OutputDebugStringA. wininet: Don't update...