similar to: Interpreter crash due to an "Unknown constant pointer type!"

Hi David, Thanks for the suggestions. I can definitely provide the example bc file and image ( please see the attachments ). For the debug + asserts I need a bit of more time. Anyway the full output of lli is: lli --force-interpreter examples/pngpixel_crash.bc 0 0 examples/mini.png png_ptr->width: 1 max_pixel_depth: 24 row_bytes: 28 Unknown constant pointer type! UNREACHABLE executed at

Hi David, In pretty sure that the crash is due to the instruction I have shared in my first email. In order to run pngpixel you just need libpng and zlib.. honest I thought that the .bc had Al the necessary. I'm happy to help you to reproduce it. As a curiosity, why do you think you cannot reproduce it? Unfortunately I won't be able to modify the interpreter soon.. anyway, I'll try to

David, sorry for this email but I noticed I made a mistake in the previous one. So I managed to compile llvm Debug with asserts release. I have used the following commands: cmake -DLLVM_TARGETS_TO_BUILD=X86 -DLLVM_ENABLE_RTTI=ON -DLLVM_ENABLE_FFI=ON -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_ASSERTIONS=ON .. cmake --build . -- -j8 && sudo cmake --build . --target install Once lli was

> > Hey Lang - does any of this look familiar to you? I'm afraid not: I know nothing about the interpreter. As far as I'm aware it's essentially abandonware. Alberto: The usual recommendation in these circumstances is to use a JIT class instead of the interpreter. You're using -force-interpreter though, so I assume you really want to use the interpreter for your use case?

Hi Alberto, Can you please file a bug for it, with the test case attached (if you haven't already). Thanks, Ehud. On Sat, 1 Feb 2020 at 11:32 Alberto Barbaro via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi all, > just a gentle reminder :) Is there any update on this please? > > Happy to help in any way I can > > Alberto > > Il giorno ven 3 gen 2020 alle

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address