search for: 3ha

Displaying 11 results from an estimated 11 matches for "3ha".

Did you mean: 3a
2020 Sep 28
2
ORC JIT - different behaviour of ExecutionSession.lookup?
...his question is different from my other question - hope this is okay. So - I was playing around with the lookup function of the ExecutionSession and there are some things I don't understand. I have a .BC file with a function "?Sampler@@YAXXZ" referencing a value "?_Plansch_test@@3HA" that is not defined in that module itself. I first planed on not providing an address for "?_Plansch_test@@3HA" but wanted to know the address of "?Sampler@@YAXXZ". So I issued something like that: auto &ES = this->jit->getExecutionSession();...
2020 Sep 29
3
ORC JIT - different behaviour of ExecutionSession.lookup?
...Mailing List <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] ORC JIT - different behaviour of ExecutionSession.lookup? Hi Bjoern, Even though the "tryToGenerate" function of my DefinitionGenerator returned a "llvm::orc::SymbolsNotFound" for the "?_Plansch_test@@3HA", I got an address for "? That's because you're issuing the lookup with RequiredState == SymbolState::Resolved. This means that your query will return as soon as "?Sampler@@YAXXZ" is assigned an address. In the JIT linker(s) addresses are assigned before external refere...
2020 Sep 30
2
ORC JIT - different behaviour of ExecutionSession.lookup?
...ause when we load stuff, we give them a hierarchical name like “Parent_Child_Child_Dino” So "?Sampler@@YAXXZ" Could be renamed to "Parent_Child_Child_Dino_?Sampler@@YAXXZ". If I encounter an undefined reference that is not part of the standard library like "?_Plansch_test@@3HA" Then I would extract the relative path and convert it to an absolute one, getting: “Parent_Child__Plansch_? test@@3HA”. When the “Plansch” module was loaded, I would have give it an unique name as well so they would fit. I would then add them to there own DyLibs and would be happy… would I?...
2020 Oct 01
2
ORC JIT - different behaviour of ExecutionSession.lookup?
...plugin to rename everything at the object file level (this is doable, as long as you have a JITLink implementation for your target platform. So far we only have MachO and ELF on x86-64. I think you need COFF, right?). 2.) Can I ask a DyLib if it has something for the “Parent_Child__Plansch_? test@@3HA" loaded? Sort of. You can look up the symbol flags for “Parent_Child__Plansch_? test@@3HA". This will not trigger materialization, but will call your definition generator to try to generate a definition. In the scheme I described above you shouldn't need to do this at all. My bigges...
2018 Mar 22
2
Broken relocation for generating offsets?
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@ jmp printf From: via llvm-dev <llvm-dev at lists.llvm.org> To: llvm-dev at lists.llvm.org Date: 06.03.2018 10:45 Subject: [ll...
2018 Mar 22
0
Broken relocation for generating offsets?
...e: > 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?$CC?5?$CFi@ > jmp printf > > > > > From: via llvm-dev <llvm-dev at lists.llvm.org> > To: llvm-dev at lists.llvm.org > Date:...
2019 Dec 09
4
IR inline assembly: the x86 Intel "offset" operator
Hi all, I'm trying to land (a rebased version of) http://llvm.org/D37461 - which should make it possible to handle x86 Intel assembly like mov eax, offset Foo::ptr + 1 (Currently, omitting the +1 works... but offset doesn't work in compound expressions.) I'm having trouble figuring out what inline assembly I can emit into the LLVM IR that will work properly. So far, the closest
2019 Dec 11
2
IR inline assembly: the x86 Intel "offset" operator
...ld be looking? On Tue, Dec 10, 2019 at 7:23 PM Reid Kleckner <rnk at google.com> wrote: > I think perhaps we want to make this LLVM IR asm string: > call void asm sideeffect inteldialect "mov eax, $0", > "i,~{eax},~{dirflag},~{fpsr},~{flags}"(i32* @"?Bar@@3HA") #1, !srcloc !3 > > The key thing is the 'i' constraint. That ends up producing the wrong > assembly right now, but maybe with your rebased patch, now it will do the > right thing. > > If you change up the dialect and switch to an ELF triple, this inline asm > wil...
2018 Mar 06
0
Broken relocation for generating offsets?
...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 offset generation seems to be broken. Executing the code coming from the object file wi...
2018 Dec 13
2
Crashes when adding VisualStduio generated object files to the JIT process
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
2018 Oct 09
3
immediate delete of mails
On Tue, 9 Oct 2018 11:09:53 +0300 Reio Remma <reio at mrstuudio.ee> wrote: > Do you see anything in Dovecot logs? It should definitely log if there > were permission issues. With 'mail_debug=yes' I see nothing relevant. Just something like this when I want to expunge deleted mails: Oct 09 10:40:01 imap(tselmeci)<15816><ZwHSosd3NL/AqAFm>: Debug: Mailbox INBOX: