search for: cygm

Good midnight, everyone! Now clang/llvm on cygming can be built selfhost with a few patch ;) I am trying to build stage2 clang/llvm with -integrated-as. I met some issues below; * MC-COFF emits .comm as individual "linkonce" section. Thus, the order in .bss must be differ against one assembled by GNU as. It might have bugs and I...

I'm trying to install llvm on my windows development box and hit a problem I'm using cygwin cygwin% gcc --version gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) I downloaded both the top of tree via svn I ran ./configure make make[1]: Entering directory `/cygdrive/c/llvm/lib/Support' llvm[1]: Compiling APFloat.cpp for Debug build llvm[1]: Compiling APInt.cpp for Debug build APInt.cpp: In member function...

On Tue, 19 Sep 2006, Anton Vayvod wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x00634572 in (anonymous namespace)::X86DAGToDAGISel::DeleteNode ( > this=0x4c3b710, N=0x4c3e5c0) > at /llvm/obj/lib/Target/X86/X86GenDAGISel.inc:77 > 77 SDNode *Operand = I->Val; > > SEGFAULT seems to come before register allocation pass is being run. Are you

2013/3/28 Anton Korobeynikov <asl at math.spbu.ru>: >> How can having an MSVC compatible compiler be to the detriment of clang and >> llvm? No one is trying to break mingw here, merely add support for something > Just to make stuff clear: I just wanted proper naming which will be > non-confusing. Right now we have: > - isTargetWindows() which really means

Good midnight, Kevin. cygming/shared might have been broken since r112976, IIRC. (ToT, too) A trivial patch; --- a/Makefile.rules +++ b/Makefile.rules @@ -942,6 +942,11 @@ ifdef EXPORTED_SYMBOL_FILE # First, set up the native export file, which may differ from the source # export file. +# The option --version-script is...

...gnara <abramo.bagnara at gmail.com>: > ../llvm-r136065/configure --host=i586-mingw32msvc > --enable-targets=host-only --disable-jit --enable-bindings=none > --enable-shared --disable-threads --disable-pthreads > --disable-assertions --disable-optimized I added --enable-shared for cygming a year ago. Anyway, I don't understand what happens to you. Lemme know; - Which distro are you using? - The version of mingw32-objdump and mingw32-ld. - Please try combination of "--enable-optimized" "--disable-embed-stdcxx". ...Takumi

Graham, good morning. To build LLVMHello on cygming, you should configure llvm with --enable-shared . Even with enable-shared, you might build lib/Transforms/Hello manually. (yeah, on cygming, LLVMHello should depend on tools/llvm-shlib) And, you'd be better to build with --enable-optimized. With enable-shared, llvm-shlib tends to fail with...

...LVM functions cannot return aggregates"" failed: file "Type.cpp", line 373 make[3]: *** [/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend/Debug/comp_ main.bc] Error 1 Any ideas? Has anybody been able to replicate this issue? GNU assembler 2.15.91 20040725 gcc (GCC) 3.4.1 (cygming special) Thanks, Oleg.

I've built LLVM/Clang from svn under Cygwin on Windows 7. I'd like to build on the LLVMHello pass example, however, when I try: $ cd $LLVM/lib/Transforms/Hello $ make I receive a large number of errors which start with: llvm[0]: Linking Debug+Asserts Loadable Module LLVMHello.dll /cygdrive/c/Users/Graham/home/projects/llvm_cygwin/lib/Transforms/Hello/Debug+Asserts/Hello.o: In function

Hi, I have successfully gotten the libshout-2.0 release to compile under gcc/MingGW ('gcc -mno-cygwin', version 'gcc (GCC) 3.3.1 (cygming special)'), after applying Leigh Smith's patches as posted on this list (http://www.xiph.org/archives/icecast-dev/0660.html). I have then generated a dll and wrapped it in JNI using the stubs from libshout-java (http://benow.ca/index?page=project&project=libshout-java). So, I have li...

Dirk, I am working on tests/win32(s) too. I can let all tests pass on msvc10 and cygming with my patches, thought, my patches are incomplete (several of them hide potential problems) Please see threads below in llvm-commits. http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20100927/109077.html http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20101004/109271.ht...

Anybody having success building an LLVM.dll in this configuration? It's failing for me, in tools/llvm-shlib, with an error suggesting that the gcc ld doesn't understand the format of the exports map being generated. (plain configure && make works just fine, it's just this shared option that fails; google shows support for --enable-shared was added around 2.7 timeframe and

Hello, I'm starting to play with LLVM today and I've trouble compiling it. I'm working under Windows Vista, with the gcc from Cygwin: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) Is LLVM supposed to work with this version of GCC (probably using the -mno-cygwin option to get a Mingw-like behavior)? The LLVM source tree is from the current SVN trunk. Compilation fails at SelectionDAG.cpp: llvm[3]: Compiling SelectionDAG.cpp for Debu...

Rubin, Norman wrote: > I'm trying to install llvm on my windows development box and hit a > problem > I'm using cygwin > cygwin% gcc --version > gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) > > I downloaded both the top of tree via svn > I ran ./configure > make > > make[1]: Entering directory `/cygdrive/c/llvm/lib/Support' > llvm[1]: Compiling APFloat.cpp for Debug build > llvm[1]: Compiling APInt.cpp for Debu...

Hi, sorry, in my last mail, I didn't check in time that HTML e-mails would be turned off. So, checking out llvm/clang yesterday under Win32, building it, and running the "check"-project using MS Visual Studio yielded 177 unexpected failures, many of which happen because of the different registers used in passing arguments under Win64 and everybody else on x86-64. I would be

...runtime, llvm-link'ing that with my frontend's .ll, and using an vcpp-built lli to run the resulting bytecode. This caused the special case in X86RegisterInfo::emitPrologue for "main" to try to align the stack using _alloca which caused the problem, because it felt that target was CygMing. Hacking the output of llvc-gcc from target triple="mingw32" to "win32" makes it "work". Is that generally dangerous, or should it be OK? I suppose I'll have to battle with msys/bison/m4 again, but they beat me soundly last time I tried to build mingw-lli. I tr...

...ot;tconfig.h ../../src/gcc/../include/ansidecl.h ../../src/gcc/config/i386/xm-cygwin.h" TM_H "tm.h ../../src/gcc/config/i386/i386.h ../../src/gcc/config/i386/unix.h ../../src/gcc/config/i386/bsd.h ./../src/gcc/config/i386/gas.h ../../src/gcc/config/dbxcoff.h ../../src/gcc/config/i386/cygming.h ../../src/g c/config/i386/cygwin.h ../../src/gcc/defaults.h insn-constants.h insn-flags.h" \ MAKEOVERRIDES= \ -f libgcc.mk all make[2]: Entering directory `/tmp/llvm3/llvm/build/gcc' for d in libgcc; do \ if [ -d $d ]; then true; else /bin/sh ../../src/gc...

...39;ing that with my frontend's .ll, > and using an vcpp-built lli to run the resulting bytecode. This caused the > special case in X86RegisterInfo::emitPrologue for "main" to try to align the > stack using _alloca which caused the problem, because it felt that target > was CygMing. Hacking the output of llvc-gcc from target triple="mingw32" to > "win32" makes it "work". Is that generally dangerous, or should it be OK? I > suppose I'll have to battle with msys/bison/m4 again, but they beat me > soundly last time I tried to build m...

...cc/libgcc2.c:43: ../../llvm-gcc/gcc/llvm-out.h:69: error: syntax error before '*' token ../../llvm-gcc/gcc/llvm-out.h:69: warning: function declaration isn't a prototype In file included from ./tm.h:9, from ../../llvm-gcc/gcc/libgcc2.c:43: ../../llvm-gcc/gcc/config/i386/cygming.h:330: error: syntax error before '*' token ../../llvm-gcc/gcc/config/i386/cygming.h:330: warning: function declaration isn't a prototype Through experimentation, running the debugger, digging through Makefiles, configure scripts, etc. I've made the following observations: 1....

Hello, Scott. > Checking the assembly from llc, the first alloca call is to allocate > local vars in _main. Is this just the state of the code at 2.0 when > built with vs.net, or is there something that I've managed to > mis-build locally? _alloca is used to probe the stack, if you asks for locals of size more that 4k. This is pretty ugly, but the names of this functions differs