search for: __imagebase

Hello, I append another clue I found out: The problem is definitely not caused by "__ImageBase" the problem comes with the "OFFSET". I generated another object file which crashed. The commonality: mov edx, DWORD PTR ?normalPlanschbecken@@3HA ; normalPlanschbecken lea rcx, OFFSET FLAT :??_C at _0CC@LCMJAIPO at Reading?5?$CCnormalPlanschbecken?$CC?5?$CFi@ jm...

...local 2GB module address range. I'm not familiar with the current JIT state of the art, though. On Thu, Mar 22, 2018 at 1:45 AM via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hello, > > I append another clue I found out: The problem is definitely not caused by > "__ImageBase" the problem comes with the "OFFSET". I generated another > object file which crashed. The commonality: > mov edx, DWORD PTR ?normalPlanschbecken@@3HA ; normalPlanschbecken > lea rcx, *OFFSET FLAT*:??_C at _0CC@LCMJAIPO > @Reading?5?$CCnormalPlanschbecken?...

...me. I'm jitting some .BC files at runtime with the LLVM under Windows 7. Thanks to the function " getImageBase()" located in RuntimeDyldCOFFX86_64.h I'm able to support exceptions. But when moving the program to Windows 10, the exceptions will crash the program. I read that the __ImageBase is important for exceptions - so what is different from Windows 7 to Windows 10? Also other __ImageBase related code - like some switch statements - also crashes under Windows10 but not under Windows7. Please help me! Kind regards Björn Als GmbH eingetragen im Handelsregister Bad Homburg v.d.H...

For x86-win32 we got __ImageBase, Is there any *simple* way to create a GlobalVariable pointing to the image base on all platforms? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160903/74cb585c/attachment-0001.html>

...ng some .BC > files at runtime with the LLVM under Windows 7. Thanks to the function " > getImageBase()" located in RuntimeDyldCOFFX86_64.h I'm able to support > exceptions. But when moving the program to Windows 10, the exceptions will > crash the program. I read that the __ImageBase is important for exceptions > - so what is different from Windows 7 to Windows 10? > > Also other __ImageBase related code - like some switch statements - also > crashes under Windows10 but not under Windows7. > > Please help me! > > Kind regards > Björn > Als GmbH ein...

...strange behavior when dealing with object files generated by the compiler of Visual Studio 2015. When jitting bc files I also add object files to look up functions. These object files are coming from visual studio. When using a switch case instruction that compiler often generates code based of __ImageBase. I show you a short snippet of the assembly output. mov eax, DWORD PTR ?myInt@@3HA ; myInt lea rdi, OFFSET FLAT:__ImageBase xor ebx, ebx Then these offset is used to jump to some labels like "$LL4 at execute:". When the object file gets added to the jitting process this...

...ents are passed to the linker. >> I tested this after creating a working llvm-dlltool. >> The only change I had to make to support this was alter ming-w64 crt to >> change all references from __image_base__ to _ImageBase to support that >> > > You may be able to define __ImageBase as a weak external symbol to > __image_base__. Then, if __ImageBase is not defined, all references against > __ImageBase will be resolved using __image_base__. > Or you could have your wrapper driver pass "/alternatename:__image_base__=__ImageBase". Peter > > >> T...

...rrect > arguments are passed to the linker. > I tested this after creating a working llvm-dlltool. > The only change I had to make to support this was alter ming-w64 crt to > change all references from __image_base__ to _ImageBase to support that > > > You may be able to define __ImageBase as a weak external symbol to > __image_base__. Then, if __ImageBase is not defined, all references against > __ImageBase will be resolved using __image_base__. > > > Or you could have your wrapper driver pass > "/alternatename:__image_base__=__ImageBase". > > >...

...rrect > arguments are passed to the linker. > I tested this after creating a working llvm-dlltool. > The only change I had to make to support this was alter ming-w64 crt to > change all references from __image_base__ to _ImageBase to support that > > > You may be able to define __ImageBase as a weak external symbol to > __image_base__. Then, if __ImageBase is not defined, all references against > __ImageBase will be resolved using __image_base__. > > > Or you could have your wrapper driver pass > "/alternatename:__image_base__=__ImageBase". > > >...

...rrect > arguments are passed to the linker. > I tested this after creating a working llvm-dlltool. > The only change I had to make to support this was alter ming-w64 crt to > change all references from __image_base__ to _ImageBase to support that > > > You may be able to define __ImageBase as a weak external symbol to > __image_base__. Then, if __ImageBase is not defined, all references against > __ImageBase will be resolved using __image_base__. > > > Or you could have your wrapper driver pass > "/alternatename:__image_base__=__ImageBase". > > >...

Hello everyone, I'm using the LLVM for a JIT-Client under Windows 64bit. I tried various stuff with it and noticed, that object files or libraries which are generated by the Visual Studio Compiler 2015 or 2017 will break the jitted code, when they are added to the process. I opened a bug for this a while ago (https://bugs.llvm.org/show_bug.cgi?id=39447) - sadly this bug will become a stopper

> > No, I meant an even thinner wrapper which textually translates arguments. > For example, the wrapper would translates "/out:foo.exe foo.obj" to "-o > foo.exe foo.obj" and then call lld::COFFF:link(). It doesn't do anything > with Config object nor LinkerDriver::run and have absolutely zero knowledge > on the internals of LLD. Ohh okay I misunderstood.

On 19.3.2013 15:49, JonY wrote: > On 3/19/2013 19:59, Janne Hyv?rinen wrote: >> On 18.3.2013 12:25, Erik de Castro Lopo wrote: >>> JonY wrote: >>> >>>> Before anyone does anything, see __wgetmainargs >>>> <http://msdn.microsoft.com/en-us/library/ff770599.aspx>. >>>> >>>> It can expand wildcards. Since it already