similar to: [LLVMdev] llvm-gcc on Cygwin

Displaying 20 results from an estimated 40000 matches similar to: "[LLVMdev] llvm-gcc on Cygwin"

2009 Jul 27
0
[LLVMdev] [Cygwin] error building llvm-gcc - X86ATTAsmPrinter error in libstdc++
This looks like pr4572. Evan On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote: > I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 > right near the end of compiling llvm-gcc in valarray-inst.cc. > > assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow > scaling by ESP" > > Does this build on Linux ? > > My
2009 Jul 26
2
[LLVMdev] [Cygwin] error building llvm-gcc
Hi Daniel, 2009/7/26 Daniel Dunbar <daniel at zuster.org> > Hi Aaron, > > Which revision are you building? 77074 >Assuming TOT, it's possible this is a bug that I introduced/triggered >with the name changes. Yes I am now getting the following :- c++ -c -g -DIN_GCC -W -Wall -Wwrite-strings -pedantic -Wno-long-long -Wno-variad ic-macros -Wmissing-format-attribute
2009 Jul 27
3
[LLVMdev] [Cygwin] error building llvm-gcc - X86ATTAsmPrinter error in libstdc++
I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 right near the end of compiling llvm-gcc in valarray-inst.cc. assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow scaling by ESP" Does this build on Linux ? My remote Linux box has died and not a ble to reset it for a day or two. /home/ang/build/llvm-gcc/./gcc/xgcc -shared-libgcc
2009 Jul 26
0
[LLVMdev] [Cygwin] error building llvm-gcc
Hi Aaron, Which revision are you building? Assuming TOT, it's possible this is a bug that I introduced/triggered with the name changes. I know nothing of the status of cygwin however, can you confirm that this used to work? If you use r77097, does it work? - Daniel On Sun, Jul 26, 2009 at 4:23 AM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > I am getting an error
2009 Feb 27
1
[LLVMdev] -fPIC warning on every compile on Cygwin
On Fri, Feb 27, 2009 at 7:14 AM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > >
2009 Mar 03
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Sun, Mar 1, 2009 at 4:24 AM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Please try this patch. I tried to copy exactly what libtool would do > on Cygwin by reading the libtool source. > > > Hi Nick, > > Working fine on Cygwin :) Great to hear! I've committed the fix in r65922.
2009 Jul 02
2
[LLVMdev] [Cygwin] Cygwin is broken again
> Hi Aaron, > > Aaron Gray <aaronngray.lists <at> googlemail.com> writes: > >> unrecognized option '--enable-runtime-pseudo-relocs' > > Interesting. > Does libCompilerDriver.dll link w/o '--enable-runtime-pseudo-relocs'? I have not tried as of yet. > If I understand correctly, this bug makes it impossible to produce > loadable >
2010 Jan 10
0
[LLVMdev] Cygwin llvm-gcc regression
2010/1/10 Aaron Gray <aaronngray.lists at googlemail.com> > 2010/1/10 Duncan Sands <baldrick at free.fr> > > Hi Aaron, >> >> >> Thanks, okay heres the results :- >>> >>> LLVM type size doesn't match GCC type size! >>> >>> <real_type 0x7ff80b40 long double sizes-gimplified XF size <integer_cst >>>
2009 Jul 03
2
[LLVMdev] [Cygwin] Cygwin is broken again
Hi Mikhail, > Aaron Gray <aaronngray.lists <at> googlemail.com> writes: >> I have not tried as of yet. > > Just compile with `make VERBOSE=1` and then copy, paste & edit > the offending line. Okay >> I don't think Cygwin supports loadable modules anyway. > > Really, Cygwin doesn't allow to produce DLLs? Then I guess I > should make this a
2009 Aug 29
0
[LLVMdev] [Cygwin] llvm-gcc-4 bug - popcountsi2.o assertion ""V == V2 && "Didn't find key?""
2009/8/28 Aaron Gray <aaronngray.lists at googlemail.com> > 2009/8/28 Anton Korobeynikov <anton at korobeynikov.info> > >> Hello, Aaron >> >> > -c /home/ang/svn/llvm-gcc-coff/gcc/libgcc2.c -o libgcc/./_popcountsi2.o >> > assertion "V == V2 && "Didn't find key?"" failed: file >> >
2009 Jul 01
4
[LLVMdev] [Cygwin] Cygwin is broken again
llvm[2]: Linking Debug Loadable Module libCompilerDriver.dll /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: unrecognized option '--enable-runtime-pseudo-relocs' /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: use the --help option for usage information collect2: ld returned 1 exit status make[2]: ***
2009 Jul 26
2
[LLVMdev] [Cygwin] error building llvm-gcc
I am getting an error building svn llvm-gcc on Cygwin :- /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ -B/usr/llv m-gcc/i686-pc-cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem /usr/llvm -gcc/i686-pc-cygwin/include -isystem /usr/llvm-gcc/i686-pc-cygwin/sys-include - O2 -I/home/ang/svn/llvm-gcc/gcc/../winsup/w32api/include -O2 -g -O2 -DIN_GCC -W -Wall
2009 Mar 02
0
[LLVMdev] Fw: -fPIC warning on every compile on Cygwin
On Sun, Mar 1, 2009 at 4:24 AM, Nick Lewycky <nicholas at mxc.ca> wrote: Please try this patch. I tried to copy exactly what libtool would do on Cygwin by reading the libtool source. Hi Nick, Working fine on Cygwin :) Aaron Nick Aaron Gray wrote: On Fri, Feb 27, 2009 at 4:50 PM, Aaron Gray <aaronngray.lists at googlemail.com <mailto:aaronngray.lists at
2009 Aug 28
2
[LLVMdev] [Cygwin] llvm-gcc-4 bug - popcountsi2.o assertion ""V == V2 && "Didn't find key?""
2009/8/28 Anton Korobeynikov <anton at korobeynikov.info> > Hello, Aaron > > > -c /home/ang/svn/llvm-gcc-coff/gcc/libgcc2.c -o libgcc/./_popcountsi2.o > > assertion "V == V2 && "Didn't find key?"" failed: file > > "/home/ang/svn/llvm-coff/ > > This is familiar but I cannot remember whether it got fixed or not now. I >
2009 Jul 02
0
[LLVMdev] [Cygwin] Cygwin is broken again
Hi Aaron, Aaron Gray <aaronngray.lists <at> googlemail.com> writes: > I have not tried as of yet. Just compile with `make VERBOSE=1` and then copy, paste & edit the offending line. > I don't think Cygwin supports loadable modules anyway. Really, Cygwin doesn't allow to produce DLLs? Then I guess I should make this a configure option.
2010 Jan 08
3
[LLVMdev] Cygwin llvm-gcc regression
I am getting an assertion firing while building TOT llvm-gcc on Cygwin in libgcc2.c :- /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ -B/home/an g/llvm-gcc/i686-pc-cygwin/bin/ -B/home/ang/llvm-gcc/i686-pc-cygwin/lib/ -isystem /home/ang/llvm-gcc/i686-pc-cygwin/include -isystem /home/ang/llvm-gcc/i686-pc-c ygwin/sys-include -O2
2009 Feb 27
0
[LLVMdev] -fPIC warning on every compile on Cygwin
On Fri, Feb 27, 2009 at 4:50 PM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Fri, Feb 27, 2009 at 4:32 PM, Jay Foad <jay.foad at gmail.com> wrote: > >> >> Could you please rig Makefile.rules or something to print out the value >> >> of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if >> >> that's
2009 Jul 02
0
[LLVMdev] [Cygwin] Cygwin is broken again
Hi Aaron, Aaron Gray <aaronngray.lists <at> googlemail.com> writes: > unrecognized option '--enable-runtime-pseudo-relocs' Interesting. Does libCompilerDriver.dll link w/o '--enable-runtime-pseudo-relocs'? If I understand correctly, this bug makes it impossible to produce loadable modules on Cygwin.
2009 Jul 03
0
[LLVMdev] [Cygwin] Cygwin is broken again
Hi Aaron, Aaron Gray <aaronngray.lists <at> googlemail.com> writes: > I sent you a _patch_ that disables it on Cygwin for the time being. LLVM > does not load DLL's properly apparently. I would love to get to the bottom > of this at some point. I've just added an --enable-llvmc-dynamic configure option (enabled only on Windows by default). This is based on your
2009 Jul 26
0
[LLVMdev] [Cygwin] error building llvm-gcc
On Sun, Jul 26, 2009 at 11:41 AM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > 2009/7/26 Daniel Dunbar <daniel at zuster.org> > lvm-backend.o > /home/ang/svn/llvm-gcc/gcc/llvm-backend.cpp: In function 'void > llvm_initialize_b > ackend()': > /home/ang/svn/llvm-gcc/gcc/llvm-backend.cpp:455: error: > 'getClosestStaticTargetF > orModule'