search for: libcor

...OTA key ============================================ TARGET_PRODUCT=generic TARGET_BUILD_VARIANT=eng TARGET_SIMULATOR= TARGET_BUILD_TYPE=release TARGET_ARCH=arm HOST_ARCH=x86 HOST_OS=linux HOST_BUILD_TYPE=release BUILD_ID= ============================================ /bin/bash: line 0: cd: dalvik/libcore//mnt/home/ganci/download/android//dalvik/libcore:/ No such file or directory /bin/bash: line 0: cd: dalvik/libcore//mnt/home/ganci/download/android//dalvik/libcore:/ No such file or directory dalvik/libcore/Android.mk:150: dalvik/libcore//mnt/home/ganci/download/android/dalvik/libcore/sub.mk:...

...;C:/home/CS/CRAN/myRlib/xps/libs/xps.dll': LoadLibrary failure: A DLL-Initialisationroutine failed. Then R crashes and Vista displays a Dialogbox with the following message: R for Windows terminal front-end does no longer function Anwendungszeitstempel: 4a928a5c Fehlermodulname: libCore.dll_unloaded Fehlermodulversion: 0.0.0.0 Fehlermodulzeitstempel: 4a4b94a1 Ausnahmecode: c0000005 Ausnahmeoffset: 0413a6f0 Betriebsystemversion: 6.0.6001.2.1.0.768.3 Gebietsschema-ID: 1031 Zusatzinformation 1: b2be Zusatzinformation 2: 82109204b3973566ace8182...

...he return value must be put in a register you were told to disable, but it's breaking soft floats in Rust on x64. It seems there are two options: LLVM could break the ABI spec and have working soft floats on 64bit or Rust could offer a configuration option to remove float support from its "libcore" (the freestanding stdlib). What do you guys think about fixing it on your end? Relevant links: Clang error w/ same message: https://llvm.org/bugs/show_bug.cgi?id=23203 Report of rust bug: https://github.com/rust-lang/rust/issues/26449 Discussion on why Rust doesn't want to fix (a refus...

Well, there is now a development branch in the git repository, which contains the infrastructure needed for rewriting the core in C. As an initial test case it simply contains a "Hello, World!" and a rewrite of rllpack in C. This is not production code in any way: SYSLINUX (the FAT version) is completely broken (I haven't had time to fix the installers yet) and the Linux kernel

...nasm -f elf -Ox -g -F dwarf -DDATE_STR="'0x5110300a'" \ -DHEXDATE="0x5110300a" \ -l isolinux.lsr -o isolinux.o -MP -MD .isolinux.o.d isolinux.asm ld -m elf_i386 -T syslinux.ld -M -o isolinux.elf isolinux.o \ --start-group libcore.a ../com32/lib/libcomcore.a /usr/lib/gcc/i386-redhat-linux/4.1.2/libgcc.a --end-group \ > isolinux.map objdump -h isolinux.elf > isolinux.sec perl lstadjust.pl isolinux.lsr isolinux.sec isolinux.lst objcopy -O binary isolinux.elf isolinux.raw ../lzo/prepcore isolinux.raw isol...

...clude:_G__cpp_setupG__Graf1 -include:_G__cpp_setupG__G3D -include:_G__cpp_setupG__GPad -include:_G__cpp_setupG__Tree -include:_G__cpp_setupG__Rint -include:_G__cpp_setupG__PostScript -include:_G__cpp_setupG__Matrix -include:_G__cpp_setupG__Physics -include:_G__cpp_setupG__Ged "C:\root/lib/libCore.lib" "C:\root/lib/libCint.lib" "C:\root/lib/libHist.lib" "C:\root/lib/libGraf.lib" "C:\root/lib/libGraf3d.lib" "C:\root/lib/libGpad.lib" "C:\root/lib/libTree.lib" "C:\root/lib/libRint.lib" "C:\root/lib/libPostscrip...

When I use llvm-2.5 to compile gnash which is a GNU flash movie player, some errors appeared as follow: llvm-ld: error: Cannot link in module '../libcore/.libs/libgnashcore.a(movie_root.o)': Linking globals named '_ZNKSt6vectorIN5gnash8geometry7Range2dIfEESaIS3_EE4sizeEv': symbols have different visibilities! Because the name is mangled, I can't find the exact position of this function in the original source code, so I can't gi...

...t of work I've done on generating source-level debugging info into a DebugInfoBuilder class like I described earlier. I went and added a new file to the "Support" directory (in include and lib). However, when I try to compile it, it complains of a circular dependency error between libCore and libSupport: find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMCore.a libLLVMSupport.a The odd part is, that no other file in LLVM even references my header, so I'm not sure where the cycle is. The headers that I am including in my .cpp file are:...

...(links with) -> TargetMachine (provides) -> CGContext So CGContext could still live inside libTarget. CGContext would be initialized for a Function based on the attributes and the information already in its container, TargetMachine. It sounds like you would be making CGContext part of libCore instead, like this: IR Transform (links with) -> LLVMContext (provides) -> CGContext CGContext would still need to be initialized with a TargetMachine, which could happen whenever the TargetMachine and Function are both available. I'm fine with that as long as - no one objects t...

...e > (provides) -> CGContext > > So CGContext could still live inside libTarget. CGContext would be > initialized for a Function based on the attributes and the information > already in its container, TargetMachine. > > It sounds like you would be making CGContext part of libCore instead, like > this: > > IR Transform > (links with) -> LLVMContext > (provides) -> CGContext > > CGContext would still need to be initialized with a TargetMachine, which > could happen whenever the TargetMachine and Function are both available. > > I'...

...d/build-utils_amd64/tools/ocaml/libs/xc/../../../../tools/libxc/libxenctrl.so: No such file or directory- build ocaml/xapi rrddump.opt Added indication that 710650 affects libxenapi-ocaml-dev > usertags 731817 piuparts There were no usertags set. Usertags are now: piuparts. > affects 731817 + libcore-ocaml-dev Bug #731817 [src:janest-core] janest-core: FTBFS with ocaml 4.01.0 Added indication that 731817 affects libcore-ocaml-dev > usertags 731400 piuparts Usertags were: piuparts. Usertags are now: piuparts. > affects 731400 + ocamlduce-base Bug #731400 [src:ocamlduce] ocamlduce: needs u...

...lds the superclass for the class inside the bitcode. (does that work at all?) the cmake should work as long as you have llvm in your path. i use "cmake . -DCMAKE_BUILD_TYPE=DEBUG" then you can run it with "bin/LLVM_JIT_Test bitcode/CMakeFiles/bitcode_mod.dir/BitcodeMod.cpp.o lib/libcore.so" (assuming you are inside the project's directory) thank you very much, stefan. -------------- next part -------------- A non-text attachment was scrubbed... Name: jit_test.tar.gz Type: application/x-compressed-tar Size: 2448 bytes Desc: not available URL: <http://lists.llvm.org/pi...

.... > > On Wed, Jun 4, 2008 at 9:12 AM, Talin <viridia at gmail.com> wrote: > > >> I went and added a new file to the "Support" >> directory (in include and lib). However, when I try to compile it, it >> complains of a circular dependency error between libCore and libSupport: >> >> find-cycles.pl: Circular dependency between *.a files: >> find-cycles.pl: libLLVMCore.a libLLVMSupport.a >> >> The odd part is, that no other file in LLVM even references my header, >> so I'm not sure where the cycle is. >&gt...

...per, but I'll give it a try... On Wed, Jun 4, 2008 at 9:12 AM, Talin <viridia at gmail.com> wrote: > I went and added a new file to the "Support" > directory (in include and lib). However, when I try to compile it, it > complains of a circular dependency error between libCore and libSupport: > > find-cycles.pl: Circular dependency between *.a files: > find-cycles.pl: libLLVMCore.a libLLVMSupport.a > > The odd part is, that no other file in LLVM even references my header, > so I'm not sure where the cycle is. The problem is not other code...

...is is not surprising, since weak linkage uses name matching and doesn't make sense for things that have no name. Updating my linkage enum port cleared that up for me. 4. The set of library names to link against has changed considerably. 5. C bindings to ExecutionEngine stuff have moved out of libCore.a.

On Mon, Oct 5, 2009 at 8:27 PM, Axel Naumann <Axel.Naumann at cern.ch> wrote: > Hi, > > #include "JIT.h" will do. Thanks. That was exactly what I needed to progress to the next error ("Unable to find target for this triple (no targets are registered)") As soon as I get this front-end working with the trunk, I'll start submitting patches that add calls to

...and stack trace saying that libclang_rt.asan-arm-android.so wasn't found. After properly preloading the ASan runtime, I see the following error message: W/Zygote ( 144): Error reading pid from wrapped process, child may have died W/Zygote ( 144): java.io.EOFException W/Zygote ( 144): at libcore.io.Streams.readFully(Streams.java:83) W/Zygote ( 144): at java.io.DataInputStream.readInt(DataInputStream.java:124) W/Zygote ( 144): at com.android.internal.os.ZygoteConnection.handleParentProc(ZygoteConnection.java:908) W/Zygote ( 144): at com.android.internal.os.ZygoteConnection.runOnce(Zy...

...hine > (provides) -> CGContext > > So CGContext could still live inside libTarget. CGContext would be > initialized for a Function based on the attributes and the information already in its container, TargetMachine. > > It sounds like you would be making CGContext part of libCore instead, like this: > > IR Transform > (links with) -> LLVMContext > (provides) -> CGContext > > CGContext would still need to be initialized with a TargetMachine, which could happen whenever the TargetMachine and Function are both available. > > I'm fine...

...at 9:12 AM, Talin <viridia at gmail.com> wrote: >> >> >>> I went and added a new file to the "Support" >>> directory (in include and lib). However, when I try to compile it, >>> it >>> complains of a circular dependency error between libCore and >>> libSupport: >>> >>> find-cycles.pl: Circular dependency between *.a files: >>> find-cycles.pl: libLLVMCore.a libLLVMSupport.a >>> >>> The odd part is, that no other file in LLVM even references my >>> header, >>...

On Mon, Dec 2, 2013 at 4:25 PM, Andrew Trick <atrick at apple.com> wrote: > > On Nov 25, 2013, at 4:40 PM, Dan Gohman <dan433584 at gmail.com> wrote: > > > Hello llvm-dev, > > > > Following up on the "CodeGen Context" discussion that was started, > attached is patch which implements a pretty minimal skeleton of a CGContext > implementation.