similar to: Position independent code writes absolute pointer

Hi Lang, On Tue, 13 Aug 2019 at 22:03, Lang Hames <lhames at gmail.com> wrote: > When you say your code is not getting optimized, do you mean that IR optimizations are not being applied, or that codegen optimizations are not being applied? > > What do you see if you dump the modules before/after running the pass manager on them, like this: > > dbgs() << "Before

Hi Lang, On Tue, 13 Aug 2019 at 23:26, Lang Hames <lhames at gmail.com> wrote: >> I also get this message: >> JIT session error: Symbols not found: { raise_error } > > > Ahh -- I see the problem. The DynamicLibrarySearchGenerator is using the getAddressOfSymbol method, which (under the hood) is basically issuing an appropriate dlsym lookup, and that does not find

Hi, I wrote a compiler that generate IR code and run it on the JIT, and there randomly crashed due to "corrupted size vs. prev_size" depends on the IR code generated from the source code. Here's how I created the JIT: llvm::InitializeNativeTarget(); llvm::InitializeNativeTargetAsmPrinter(); llvm::InitializeNativeTargetAsmParser(); // create jit llvm::orc::ExecutionSession

Hey Lang, Woah! That mail contains a lot of information and things I never tried yet… Actually… the entire MaterializationUnit and MaterializationResponsibility part is… quite… overwhelming >O< With “pop up” I mean… the process which is waiting for Module “Planschi” to “pop up” can not do a thing about it. It just waits until there is an table entry for it, indicating that the object file

On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: > You were proposing to use a valid/existing MagicValue/Version/VendorID with a > special DeviceID that does nothing. I'm saying why not use a valid/existing > MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0, > that does nothing? Ah, I see. Well, it sounds from your

On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: > You were proposing to use a valid/existing MagicValue/Version/VendorID with a > special DeviceID that does nothing. I'm saying why not use a valid/existing > MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0, > that does nothing? Ah, I see. Well, it sounds from your

On Thu, 2013-06-20 at 11:29 +0100, Peter Maydell wrote: > I'm (finally) trying to add virtio-mmio support properly to > QEMU now Fred has put all the refactoring foundations in place. > > 1. One question I've run into is: what should a virtio-mmio transport > with no backend look like to the guest OS? The spec as written > seems to assume that there's always some

On Thu, 2013-06-20 at 11:29 +0100, Peter Maydell wrote: > I'm (finally) trying to add virtio-mmio support properly to > QEMU now Fred has put all the refactoring foundations in place. > > 1. One question I've run into is: what should a virtio-mmio transport > with no backend look like to the guest OS? The spec as written > seems to assume that there's always some

Hey Lang, > Do you mean that the object file is produced by another process and is being loaded into your JIT process for execution, or that you want your JIT to produce code for several different processes? These are different problems with different solutions. I'll wait until I understand your use case to answer further. In the current state we don’t have a JIT only an handcrafted object

Hi Lang, On Tue, 13 Aug 2019 at 20:47, Lang Hames <lhames at gmail.com> wrote: > > Sorry for the delayed reply. Looks like you have figured out how to solve your issue already. Out of interest, what did you need to do? Do you have anything that you would like to see added to http://llvm.org/docs/ORCv2.html ? > Sorry my post was misleading. I figured out below which was part of the

On 21 June 2013 19:01, Christopher Covington <cov at codeaurora.org> wrote: > Anyhow, I just did a quick experiment with 0-size block devices, and they seem > to work for me, although trying to mount the device yields the confusing > message, "mount: mounting /dev/vda on mount failed: Invalid argument". I'm confused -- what's the significance of zero size block

On 21 June 2013 19:01, Christopher Covington <cov at codeaurora.org> wrote: > Anyhow, I just did a quick experiment with 0-size block devices, and they seem > to work for me, although trying to mount the device yields the confusing > message, "mount: mounting /dev/vda on mount failed: Invalid argument". I'm confused -- what's the significance of zero size block

Hi, "Appendix X: virtio-mmio" in the virtio spec says ? 0x040 | RW | QueuePFN [...] When the Guest stops using the queue it must write zero (0x0) to this register. [...] and Virtqueue Configuration [...] 2. Check if the queue is not already in use: read QueuePFN register, returned value should be zero (0x0). [...] I think this in itself is

Hi, "Appendix X: virtio-mmio" in the virtio spec says ? 0x040 | RW | QueuePFN [...] When the Guest stops using the queue it must write zero (0x0) to this register. [...] and Virtqueue Configuration [...] 2. Check if the queue is not already in use: read QueuePFN register, returned value should be zero (0x0). [...] I think this in itself is

Hi, I'm trying to access a share on my work network using smbclient. We have an Windows Active Directory network. My client computer is running Solaris 10 u8. The computer hosting the share says it's running Acopia ARX(3.0.0b1) According to Active Directory (not familiar with this OS, i think it is a NAS) I run this command to get the Kerberos ticket. bash-3.00$ kinit jtmb at

Hi Peter, On 06/20/2013 07:08 AM, Pawel Moll wrote: > On Thu, 2013-06-20 at 11:29 +0100, Peter Maydell wrote: >> I'm (finally) trying to add virtio-mmio support properly to >> QEMU now Fred has put all the refactoring foundations in place. >> >> 1. One question I've run into is: what should a virtio-mmio transport >> with no backend look like to the guest

On 06/21/2013 02:28 PM, Peter Maydell wrote: > On 21 June 2013 19:01, Christopher Covington <cov at codeaurora.org> wrote: >> Anyhow, I just did a quick experiment with 0-size block devices, and they seem >> to work for me, although trying to mount the device yields the confusing >> message, "mount: mounting /dev/vda on mount failed: Invalid argument". >

On 06/22/2013 06:51 AM, Peter Maydell wrote: > On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: >> You were proposing to use a valid/existing MagicValue/Version/VendorID with a >> special DeviceID that does nothing. I'm saying why not use a valid/existing >> MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0,

Hey Lang, I would be really happy to only have one LLJIT instance and using multiple JITDylibs. However… it seems like that I don’t know enough to use them. So I wonder… 1. When I add Module A to JITDylib A and Module B to JITDylib B – where will those look for undefined symbols? Will Module A for example: will it only search itself and the MainDylib? Or would it also search in JITDylib B?

Hey Lang, Thank you for your help and your patience – also for your answers in the “ORC JIT - Can modules independently managed with one LLJIT instance? + problems with ExecutionSession.lookup” mail. Both problems have the same origin so I keep writing about it here, to avoid duplication. My big problem is still handling cross references between modules with “our” name scheme. Since our old