similar to: [LLVMdev] LLVM 3.1 type linking?

Hi again, I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To do so, I regenerated the JNI bindings from fresh LLVM 3.1 headers, and did a slight rewrite of my CMakeLists.txt file for building the C code. Problem is, cmake no longer finishes at all. I receive the following output, and then it just runs forever (while still responding to a CTRL-C): > eli at

Eli Gottlieb <eligottlieb at gmail.com> writes: > I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To > do so, I regenerated the JNI bindings from fresh LLVM 3.1 headers, and > did a slight rewrite of my CMakeLists.txt file for building the C > code. > > Problem is, cmake no longer finishes at all. I receive the > following output, and then

Eli Gottlieb <eligottlieb at gmail.com> writes: > So you're saying that the default CMake build of LLVM creates static > libraries that got linked into my shared-object and now require me to > link in everything they require myself? Shouldn't the linker be able > to track down C++ runtime for this? You told CMake to manage your shared library as if it were a pure C

Eli Gottlieb <eligottlieb at gmail.com> writes: > I compiled and installed it to the prefix /usr, but that's not the > issue. Once I actually compile and install LLVM with CMake by hand, I > get the share/llvm/cmake stuff installed correctly (can those files be > included in "normal" builds, or will LLVM switch to CMake as its > primary build system?). Now

After I actually get everything compiling, install the library, and load it from my Java program, I get the following: > Exception in thread "main" java.lang.UnsatisfiedLinkError: > /usr/lib/libjllvm.so: /usr/lib/libjllvm.so: undefined symbol: > _ZTVN10__cxxabiv120__si_class_type_infoE If I have to guess, this means that the CMake stuff given is linking to the C++ libraries

On Nov 4, 2010, at 11:48 AM, Óscar Fuentes wrote: > Eli Gottlieb <eligottlieb at gmail.com> writes: > >> So you're saying that the default CMake build of LLVM creates static >> libraries that got linked into my shared-object and now require me to >> link in everything they require myself? Shouldn't the linker be able >> to track down C++ runtime for

Well for one thing, it gives one example of a CMakeLists.txt file that correctly uses LLVM, and nothing else. It gives no information on how to find out what set of components I need to map for what APIs. Neither does llvm-config list out the names of the actual components. I can use either the CMake modules or llvm-config to find the library names once I've got the component names, but

[Please CC the mailing list] Eli Gottlieb <eligottlieb at gmail.com> writes: > OK, I'm just going to paste in my CMakeLists.txt file. Like I said, > I'm building an LLVM install myself by untarring llvm, mkdir build in > the root dir of the source, cd build/, cmake .., make. > >> cmake_minimum_required (VERSION 2.6) >> project (libjllvm) >>

Eli Gottlieb <eligottlieb at gmail.com> writes: > The two lines >> set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} >> "${LLVM_ROOT}/share/llvm/cmake") >> include(LLVM) > don't seem to work. I'm checking with installing LLVM from source to > see if that makes it work, but the LLVM install from the Ubuntu repos > doesn't seem to have a

I have a directory dumps on my laptop containing several dumps of various levels. local-0-2007-03-03.gz local-4-2007-02-12.gz local-4-2007-02-19.gz local-4-2007-02-26.gz local-4-2007-03-05.gz local-5-2007-03-04.gz local-5-2007-03-06.gz local-5-2007-03-07.gz local-5-2007-03-08.gz Naturally the level-0 is the largest and rarely changes. On the target (access.cims.nyu.edu) I have a directory

Hi, My name's Eli Gottlieb, and I've got a proposal for GSOC. I've noticed that the LLVM IR-generation libraries currently only have bindings in C, C++, and OCaml. Would you like me to write bindings in Java for them? Sincerely, Eli Gottlieb UMass Amherst Computer Science, 2011

Consider the following test case: %struct.A = type opaque @g = external global [0 x %struct.A] declare void @foo(%struct.A*) define void @f() uwtable ssp align 64 { %x = getelementptr [0 x %struct.A]* @g, i32 0, i32 0 call void @foo(%struct.A* %x) ret void } Before the type system rewrite, we would accept this construct; now, we reject it. (This leads to clang/opt crashing on certain

It would be prudent the test for success and continue rather than failure and drop. For example: exten => s,5,GotoIf($["${SYSTEMSTATUS}" != "SUCCESS"]?105:6) That way only the result that you know is good, Will continue a call.. > -----Original Message----- > From: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On

Hi All, I am encountering the following error "assigning to 'uint4' from incompatible type 'int __attribute__((ext_vector_type(4)))'" for code, p = q < (uint4)2; where p and q are of type uint4 The explicit type casting before assignement [p = (unit4)(q < (uint4)2)] resolves the error. In Clang Rev 2.9, there was no error for such code. Avoiding this implicit

Zitat von Israel Gottlieb <isrlgb at gmail.com>: > If you the c option in the dial command it will send answered > else where sip message to the phone and most ip phones understand that > The cell will always display a missed call? I'm very sorry, but I can't understand what you mean... Could you explain, maybe with an example? Thanks Luca Bertoncello (lucabert at

> On Mar 26, 2018, at 17:09, Andres Freund <andres at anarazel.de> wrote: > > Hi, > > On 2018-03-26 16:44:05 -0700, Duncan P. N. Exon Smith wrote: >>> The second approach is to *not* cache modules but re-read them from disk >>> (or memory, but that's irrelevant here). That works without any sort of >>> asserts, but "leaks" memory

I compiled and installed it to the prefix /usr, but that's not the issue. Once I actually compile and install LLVM with CMake by hand, I get the share/llvm/cmake stuff installed correctly (can those files be included in "normal" builds, or will LLVM switch to CMake as its primary build system?). Now I'm running into the problem of cflags or includes or something not being

There is an issue with representing opaque types in LLVM IR modules: if two modules are using the same opaque type (which is only going to be specialised at some later stage), it is only identified by its name. But the current module linker "resolves" this as if there is a name clash, and one of that opaque types is renamed. It contradicts an intuitively expected identifier behaviour

On Mon, Jul 25, 2011 at 8:52 AM, Anton Lokhmotov <Anton.Lokhmotov at arm.com>wrote: > There is an issue with representing opaque types in LLVM IR modules: if two > modules are using the same opaque type (which is only going to be > specialised at some later stage), it is only identified by its name. But > the current module linker "resolves" this as if there is a name

On 2003-04-26 at 00:42, Jim Gottlieb (that's me) wrote: > [ccmenu] > exten=s,1,Ringing > exten=s,2,Wait,2 > exten=s,3,BackGround(5045) > exten=s,4,Goto,outtrunk|17005554223|1 ; if they just wait > exten=_X,1,Goto,outtrunk|17005554223|1 ; if they press 0-9 > exten=_*,1,Goto,outtrunk|17005554223|1 ; if they press * > exten=_#,1,Goto,outtrunk|17005554223|1 ; if they