similar to: [LLVMdev] dragonegg plugin invoking issue

Hi Rehman, if I understand right the plugin works fine if you compile it with -fvisibility=hidden, and replace LLVM_GLOBAL_VISIBILITY in llvm-backend.cpp with __attribute__ ((visibility("default"))). Since LLVM_GLOBAL_VISIBILITY is a macro that expands to __attribute__ ((visibility("default"))) if you are not on mingw32 or cygwin, and your gcc version is at least 4, that

On Fri, Dec 07, 2012 at 06:20:37PM +0100, Duncan Sands wrote: > Hi Jack, this occurs because you compiled LLVM with clang (right?) and > dragonegg is compiled with the same flags used to compile LLVM (it is > an llvm-config bug in my opinion that llvm-config output includes these > kinds of optional flags). Duncan, Yes. I believe both fink and MacPorts now default to the clang

Hi Jack, can you please open a bug report asking that llvm-config only provide the minimum set of flags needed to compile code that interfaces with LLVM, rather than (as now) all kinds of unneeded flags such as -g and warnings. Thanks, Duncan. On 07/12/12 18:55, Jack Howarth wrote: > On Fri, Dec 07, 2012 at 06:20:37PM +0100, Duncan Sands wrote: >> Hi Jack, this occurs because you

Hi Jack, this occurs because you compiled LLVM with clang (right?) and dragonegg is compiled with the same flags used to compile LLVM (it is an llvm-config bug in my opinion that llvm-config output includes these kinds of optional flags). Ciao, Duncan. On 07/12/12 18:11, Jack Howarth wrote: > Duncan, > I am unable to complile dragonegg 3.2 with FSF gcc 4.7 due the the > compiler

Duncan, I am unable to complile dragonegg 3.2 with FSF gcc 4.7 due the the compiler errors... GCC=/sw/lib/gcc4.7/bin/gcc-4 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config VERBOSE=1 ENABLE_LLVM_PLUGINS=1 make CPPFLAGS="-g -DENABLE_LTO -I/sw/include" /sw/lib/gcc4.7/bin/gcc-4 --version > /dev/null /sw/opt/llvm-3.2/bin/llvm-config --version > /dev/null Compiling utils/TargetInfo.cpp

Hi all, Sorry for the inconvenient about the previous post. The files were not attached. So I put them here again. I am a newbie in LLVM and I am trying to replace the function like: old function || new function ============================== ========= int haha(int a) { int haha(int a, char* ID) { ===> }

> Is there anything I can do to make the build more verbose so I can debug this? make VERBOSE=1

Dears I have installed Ruby and Rails succesfuuly but when I run it on the browser by typing http://localhost:3000/, it gives an error ("The Page cannot be displyed"). PLease help me in this regard. Shakeel ur Rehman -- Posted via http://www.ruby-forum.com/.

On Fri, Dec 07, 2012 at 06:57:36PM +0100, Duncan Sands wrote: > Hi Jack, can you please open a bug report asking that llvm-config only > provide the minimum set of flags needed to compile code that interfaces > with LLVM, rather than (as now) all kinds of unneeded flags such as -g > and warnings. > > Thanks, Duncan. > Duncan, I have opened

Hi, I'm trying to compile some apps with the new llvm-gcc4 on amd64 linux to .bc files, rather than to the native code. The same process I used to build those apps before with llvm-gcc3 doesn't work: 1) export CC=llvm-gcc CXX=llvm-g++ CFLAGS="-g -fno-inline" CXXFLAGS="-g -fno-inline" 2) cd <whatever-app>; ./configure 3) make CFLAGS+=-emit-llvm

On 3 Jan 2018, at 18:24, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I'd like to propose that trunk always have a version number which is in between versions used by the previous release branch, and before the versions used in the next release branch. > > Right now, trunk is sharing the 7.0.0 number, which will also be used by the next release 4

On Thu, Jan 4, 2018 at 3:04 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 3 Jan 2018, at 18:24, James Y Knight via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > I'd like to propose that trunk always have a version number which is in > between versions used by the previous release branch, and before the > versions used in the next release

Hi, I am learning cucumber. I have integrated the Devise with my rails 3 application. My problem is I have to write a test which will create a project. For that I have to make sure that user should be logged in. So I have written the user login feature first which is working fine. After that I have written the creation of project scenario. Whenever I am running that scenario we are getting an

Hi all, I have some code that uses the x86 JIT via the C bindings that I'm trying to migrate from targeting LLVM 2.5 to the top of tree, but I'm running into a linking problem I can't figure out. Here's how I'm invoking the JIT in 2.5. LLVMInitializeNativeTarget(); <-- for the updated version LLVMCreateMemoryBufferWithContentsOfFile("code.bc", &buffer,

On 11/14/2017, 01:26 AM, Chris Bieneman wrote: > Sorry for the delayed response. I've been out of town a lot lately. > > The documentation you referenced is unfortunately out of date (you might notice it still references autoconf). I'll see if I can find time to update it, but the guidance should be to use the `llvm_config` CMake function instead. The proper usage of that in the

Hi, In SUSE we have recently switched from building LLVM as multiple shared libraries (using BUILD_SHARED_LIBS) to building it as a single shared library (using LLVM_BUILD_LLVM_DYLIB). The multiple shared libraries build was causing issues and apparently it is only meant for LLVM developers. Our guidelines prohibit linking against static libraries unless there is no other option. After this

Keppler, Dave wrote: > Hi all, > > I have some code that uses the x86 JIT via the C bindings that I'm trying to migrate from targeting LLVM 2.5 to the top of tree, but I'm running into a linking problem I can't figure out. > > Here's how I'm invoking the JIT in 2.5. > > LLVMInitializeNativeTarget(); <-- for the updated version >

>> I'm compiling it as follows, which completes with no errors on either >LLVM version. >> >> LLVM_CONFIG=<the llvm-config from the version I want to use> >> gcc `$LLVM_CONFIG --cflags` -o main.o -c main.c >> g++ `$LLVM_CONFIG --cflags` \ >> `$LLVM_CONFIG --ldflags` \ >> main.o `$(LLVM_CONFIG) --libfiles engine BitReader` >>

Hi, I have some problems with the debug build. I cannot use 'call F->viewCFG()', gdb says the function might be inlined. Did not help with make CXXFLAGS+="-O0 -g3". I also have problems setting breakpoints in gdb for methods. I expected this functionality in a Debug build, pleas give any info /Jonas -------------- next part -------------- An HTML attachment was

I have an issue with the OCaml build system and the ExecutionEngine. PR2128 has a patch to change the Interpreter to use libffi. This breaks test/Bindings/Ocaml/executionengine.ml because OCaml doesn't try to link with libffi, even though llvm-config knows that we should: $ Debug/bin/llvm-config --ldflags interpreter -L/home/nicholas/llvm-commit/Debug/lib -lpthread -lffi -ldl -lm