search for: robovm

...e resulting obj files) using llvm 3.4 for both unix and windows. And I use the dreaded weak references, that, for windows, are not too widely supported. When I link my application on linux, I have no issue. But when I'm doing the same on windows using mingw I got a duplicate symbol error : ..\robovm-0.0.8\lib\robovm-rt.jar\dalvik\system\BlockGuard$BlockGuardPolicyException.class.o:(.text$dalvik_system_BlockGuard$24BlockGuardPolicyException_getPolicy__I_lookup[_dalvik_system_BlockGuard$24BlockGuardPolicyException_getPolicy__I_lookup]+0x0): multiple definition of `dalvik_system_BlockGuard$24Bloc...

...gt; And I use the dreaded weak references, that, for windows, are not too >> widely supported. >> >> When I link my application on linux, I have no issue. >> But when I'm doing the same on windows using mingw I got a duplicate >> symbol error : >> >> ..\robovm-0.0.8\lib\robovm-rt.jar\dalvik\system\BlockGuard$BlockGuardPolicyException.class.o:(.text$dalvik_system_BlockGuard$24BlockGuardPolicyException_getPolicy__I_lookup[_dalvik_system_BlockGuard$24BlockGuardPolicyException_getPolicy__I_lookup]+0x0): >> multiple definition of >> `dalvik_system...

...dows, are not too >>>> widely supported. >>>> >>>> When I link my application on linux, I have no issue. >>>> But when I'm doing the same on windows using mingw I got a duplicate >>>> symbol error : >>>> >>>> ..\robovm-0.0.8\lib\robovm-rt.jar\dalvik\system\BlockGuard$BlockGuardPolicyException.class.o:(.text$dalvik_system_BlockGuard$24BlockGuardPolicyException_getPolicy__I_lookup[_dalvik_system_BlockGuard$24BlockGuardPolicyException_getPolicy__I_lookup]+0x0): >>>> multiple definition of >>>&gt...

...van.cheng at apple.com> wrote: > > Hi Niklas, > > The attached patch has nothing to do with register allocation. r206094 changes how cpu auto-detection is done. I believe it's now the responsibility of the tools (e.g. llc) to detect the cpu. My guess is the proper fix is on the RoboVM side to handle the change. > > Jim, can you confirm? > > Evan > > On Jun 1, 2014, at 1:45 PM, Niklas Therning <niklas at therning.org> wrote: > >> I think we have located the revision which fixes this regression: r206094 (or commit 6bb00df in llvm-mirror on GitH...

...alloc-test.ll file doesn't fail with the "LLVM ERROR: ran out of registers during register allocation" error any longer. I haven't run any llvm tests to make sure this patch doesn't break anything else but as far as I can see it doesn't at least break anything when used in RoboVM. Is it too late to get this into 3.4.2? Is there anything else I can do to make it easier for you to include this patch in 3.4.2 or the next possible point release? On Wed, May 14, 2014 at 3:25 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 14 May 2014 14:15, Niklas Thernin...

Hi, The RoboVM project recently upgraded from LLVM 3.3 to 3.4 and with the new version we are sometimes seeing "ran out of registers during register allocation" errors when targeting x86 32-bit that we haven't seen before. Nothing has changed in our bitcode generator. I have attached an IR file whic...

...rks for me with trunk r207129. > > We did fix some register allocation issues recently, don’t know which > change fixes the issue though. > > Thanks, > -Quentin > > On Apr 24, 2014, at 1:07 PM, Niklas Therning <niklas at therning.org> wrote: > > Hi, > > The RoboVM project recently upgraded from LLVM 3.3 to 3.4 and with the new > version we are sometimes seeing "ran out of registers during register > allocation" errors when targeting x86 32-bit that we haven't seen before. > Nothing has changed in our bitcode generator. I have attached...

...m = output.toByteArray(); BufferedOutputStream oOut = new BufferedOutputStream(new FileOutputStream(oFile)); targetMachine.assemble(asm, clazz.getClassName(), oOut); oOut.close(); (I use a java binding for llvm) Unfortunately, the assemble call fails with the error: org.robovm.llvm.LlvmException: java.io.PrintWriter:478:2: error: unknown directive .section .text$java_io_PrintWriter_checkError__Z_lookup,"xr" ^ java.io.PrintWriter:479:2: error: unknown directive .linkonce discard ^ java.io.PrintWriter:629:2: error: unknown directiv...

I recently subscribed to the LLVM and Clang developer mailing lists, and earlier today read a message requesting advice on "Contributing to LLVM Projects". I'm hoping to eventually get involved as well, but with my situation being very different to that described in the referenced thread I got the idea of solliciting advice seperately. If this is not the right place to ask, though,