similar to: [LLVMdev] DragonEgg on FreeBSD

Displaying 20 results from an estimated 300 matches similar to: "[LLVMdev] DragonEgg on FreeBSD"

2011 Jan 08
0
[LLVMdev] DragonEgg on FreeBSD
Hi chenwj, > I have made DragonEgg supports FreeBSD 8.1. May someone like > to a look? :) great! Does it work ok? If you had to make any changes to dragonegg, please send patches to the mailing list. If there are some tricks needed to get it to build, please explain what you had to do and these can be mentioned in the dragonegg README and on the web-site. Ciao, Duncan.
2014 Sep 11
3
[LLVMdev] patch for DragonEgg 3.3
Hi - attached is a patch to enable building DragonEgg (x86_64) for LLVM3.3 and LLVM3.4. That is, add these changes to the 3.3 release, and it becomes possible to build DragonEgg against a llvm3.4 compiler. Regards, Richard Gorton Cognitive Electronics rcgorton at cog-e.com ---------- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:
2011 Jan 09
1
[LLVMdev] DragonEgg on FreeBSD
Hi, Duncan I only tested dragonegg on simple HelloWorld C/C++ programs. It can emit LLVM IR and generate a runable executable. On FreeBSD, Makefile need to be modified to include a path to gmp.h header file. I give a patch here, -------------------------------------------------------------------------------- --- Makefile.orig 2011-01-08 12:39:35.480184745 +0800 +++ Makefile
2011 Apr 08
4
[LLVMdev] dragonegg build failure
> Is there anything I can do to make the build more verbose so I can debug this? make VERBOSE=1
2011 Apr 18
0
[LLVMdev] [EXPERIMENTAL] Building Dragonegg on Cygwin
Good evening, guys! I have built dragonegg.dll on cygwin and it works (it seems). I have not tried stage2 build yet. It would be applicable to also mingw32-gcc to enhance gcc/plugin.c. ...Takumi [Instructions] 1. Apply two patches. one is for gcc/config/i386/i386.c. --- a/gcc/configure +++ b/gcc/configure @@ -25621,6 +25621,9 @@ rm -f core conftest.err conftest.$ac_objext \ fi
2012 Dec 07
2
[LLVMdev] dragonegg now requires clang
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
2011 Sep 16
2
[LLVMdev] How to duplicate a function?
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) { ===> }
2012 Dec 07
2
[LLVMdev] dragonegg now requires clang
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
2012 Dec 07
0
[LLVMdev] dragonegg now requires clang
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
2012 Dec 07
0
[LLVMdev] dragonegg now requires 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
2011 Apr 08
0
[LLVMdev] dragonegg build failure
On Fri, Apr 08, 2011 at 01:58:10PM +0200, Duncan Sands wrote: >> Is there anything I can do to make the build more verbose so I can debug this? > > make VERBOSE=1 Duncan, Oddly this shows... GCC=/sw/lib/gcc4.5/bin/gcc-4 LLVM_CONFIG=/sw/bin/llvm-config make VERBOSE=1 CPPFLAGS="-DENABLE_LTO -I/sw/include" Compiling utils/TargetInfo.cpp g++ -c
2004 Jul 27
1
warning killing for poor !LANG=C|US people
--- ../multipath-tools-0.2.8.1/klibc/klibc/arch/i386/MCONFIG 2004-07-20 10:51:42.000000000 +0200 +++ klibc/klibc/arch/i386/MCONFIG 2004-07-27 17:10:12.000000000 +0200 @@ -13,7 +13,7 @@ # them to be cdecl # REGPARM = -mregparm=3 -DREGPARM -gcc_major := $(shell $(CC) -v 2>&1 | awk '/gcc version/{print int($$3)}') +gcc_major := $(shell unset LANG;$(CC) -v 2>&1 | awk
2005 Feb 10
2
[LLVMdev] Add ability for external projects use for build installed version LLVM [PATCH]
> Vladimir, > > I took a *very quick* look at your patch. I won't be able to look at it in > more detail until this weekend, but perhaps you can address a couple of > concerns: > > 1. I don't understand the need for LLVMToolDirSlash. This seems like a > gratuitous change to me. If LLVM_OBJ_ROOT (with LLVM_SRC_ROOT) and LLVM_ROOT both not set without
2005 Feb 11
0
[LLVMdev] Add ability for external projects use for buildinstalled version LLVM [PATCH]
>> Before this change is committed, you need to test that all our scenarios, >> in each combination: >> >> 1. Both with and without OBJ_DIR == SRC_DIR >> 2. Single and Parallel builds >> 3. Building LLVM versus building a project (and now building from >> installed) > ok, will do... > > I found some bugs in my patch and then I will send updated
2020 Mar 27
3
llvm-objdump cannot recognize mul&mulh RISC-V M Instructions
I am using llvm-project compiling risc-v programs. llvm-project version:dd8a2013dc1804be1b7d9cffacad2e984300bd22 Instructons to build LLVM+clang: ``` cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/home/llvm/workspace/llvm/llvm-project/llvm_install -DCMAKE_BUILD_TYPE="Release" -DDEFAULT_SYSROOT="/home/llvm/workspace/riscv/riscv-tc-20200220/bin/riscv32-unknown-elf"
2002 Aug 23
3
Filenames with blanks
Command like this: rsync -rxlupogtSvve ssh $src_host:"/home/wss_disk/calendar.data/'Conference Calls'" $targ_dir works fine with blanks embeded in the file name. When I try to script it like this: COM='`find '$src_dir' -mtime -'$days' -type f `' rsync -rxlupogtSvve ssh $src_host:"$COM" $targ_dir works fine on regular filenames,
2010 Apr 10
3
[LLVMdev] darwin dragon-egg build issues
Is anyone building dragon-egg on darwin? I am trying to build against the fink gcc45 package that I have prepared for darwin and a updated fink llvm 2.7 package that is built as... ../llvm-2.7/configure --prefix=/sw --prefix=/sw/lib/llvm --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw --with-libiconv-prefix=/usr --with-system-zlib --with-as=/Developer/usr/bin/as
2011 Jan 18
3
[LLVMdev] About test suits Cont1
*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk
2011 Jan 17
0
[LLVMdev] About test suits Cont1
On Jan 15, 2011, at 8:06 PM, Qingan Li wrote: > [qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {} \; > ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) > ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S
2010 Apr 11
7
[LLVMdev] darwin dragon-egg build issues
On Sat, Apr 10, 2010 at 01:52:18PM +0200, Duncan Sands wrote: > Hi Jack, > > > Is anyone building dragon-egg on darwin? > > Anton built it once. There were some problems with dynamic libraries: gcc's > plugin support requires the use of dynamic libraries, and the configure logic > it uses thinks that darwin does not support dynamic libraries! So it is >