similar to: [LLVMdev] [Cygwin] Cygwin 'make check' failures

Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] [Cygwin] Cygwin 'make check' failures"

2011 Jun 15
0
[LLVMdev] Custom allocation orders
The target description .td files are allowed to change the default allocation order on a register class by overriding the allocation_order_begin() and allocation_order_end() methods on TargetRegisterClass. Previously, this was used all the time to filter out stack and frame pointers and other reserved registers. I was able to remove most of these custom allocation orders in the tree because the
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
2007 Oct 05
0
[LLVMdev] RFC: Tail call optimization X86
Hi Evan, I incoporated the changes you request but to the following i have got a question: > Also, moving the option > there will allow us to change fastcc ABI (callee popping arguments) > only when this option is on. See Chris' email: I am not to sure on that. because that would make modules compiled with the flag on incompatible with ones compiled without the flag off as
2009 May 28
0
[LLVMdev] [Cygwin] OCAML 'make check' failures
Getting the following on Cygwin :- Running /home/ang/svn/llvm/test/Bindings/Ocaml/ocaml.exp ... FAIL: /home/ang/svn/llvm/test/Bindings/Ocaml/analysis.ml Failed with exit(2) at line 1 while running: /usr/bin/ocamlc -cc g++ -I /home/ang/build/llvm/Debug/lib/ocaml - warn-error A llvm.cma llvm_analysis.cma /home/ang/svn/llvm/test/Bindings/Ocaml/a nalysis.ml -o analysis.ml.tmp 2> /dev/null child
2007 Oct 05
0
[LLVMdev] RFC: Tail call optimization X86
On Oct 5, 2007, at 10:41 AM, Evan Cheng wrote: > > On Oct 5, 2007, at 2:42 AM, Arnold Schwaighofer wrote: > >> Hi Evan, >> I incoporated the changes you request but to the following i have got >> a question: >> >>> Also, moving the option >>> there will allow us to change fastcc ABI (callee popping arguments) >>> only when this option is
2009 Aug 28
2
[LLVMdev] [Cygwin] llvm-gcc-4 bug - popcountsi2.o assertion ""V == V2 && "Didn't find key?""
/home/ang/build/llvm-gcc-coff/./gcc/xgcc -B/home/ang/build/llvm-gcc-coff/./gcc/ -B/home/ang/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-cygwin/sys-include -O2 -I/home/ang/svn/llvm-gcc-coff/gcc/../winsup/w32 api/include -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings
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
2008 Mar 27
0
[LLVMdev] llvm-gcc 4.2 assertion failed on linux x86_64
Does this fix it? Index: lib/Target/X86/X86Subtarget.h =================================================================== --- lib/Target/X86/X86Subtarget.h (revision 48879) +++ lib/Target/X86/X86Subtarget.h (working copy) @@ -144,9 +144,12 @@ std::string getDataLayout() const { const char *p; - if (is64Bit()) - p = "e-p:64:64-s:64-f64:64:64-i64:64:64-f80:128:128"; -
2008 Mar 27
1
[LLVMdev] llvm-gcc 4.2 assertion failed on linux x86_64
Probably better to move the discussion to a bug? Evan On Mar 27, 2008, at 9:04 AM, Duncan Sands wrote: > Does this fix it? > > Index: lib/Target/X86/X86Subtarget.h > =================================================================== > --- lib/Target/X86/X86Subtarget.h (revision 48879) > +++ lib/Target/X86/X86Subtarget.h (working copy) > @@ -144,9 +144,12 @@ > >
2009 Aug 28
1
[LLVMdev] [Cygwin] 'make install' woes
I am getting the following on 'make install' on Cygwin both on debug and release builds :- llvm[3]: Installing Release /home/ang/llvm-coff/bin/llvmc.exe make[3]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc/driver' make[2]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc' make[1]: Leaving directory `/home/ang/build/llvm-coff/tools' make[1]: Entering
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 23
1
[LLVMdev] 2.5 Pre-release2 available for testing
On Mon, Feb 23, 2009 at 12:12 AM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < > anton at korobeynikov.info> wrote: > >> >> Actually its [configure-stage3-intl] where its hanging. >> >> This can easily be due to inline FP math in the stdlib headers. For >> example - I had to
2009 Jun 10
3
[LLVMdev] Why does the x86-64 JIT emit stubs for external calls?
In X86CodeGen.cpp, the following code appears in the handler used for CALL64pcrel32 instructions: // Assume undefined functions may be outside the Small codespace. bool NeedStub = (Is64BitMode && (TM.getCodeModel() == CodeModel::Large || TM.getSubtarget<X86Subtarget>().isTargetDarwin())) || Opcode == X86::TAILJMPd;
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
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
2010 Mar 06
0
[LLVMdev] Cygwin patches for 2.7
On 6 March 2010 11:16, Aaron Gray <aaronngray.lists at googlemail.com> wrote: > On 6 March 2010 10:47, Eric Christopher <echristo at apple.com> wrote: > >> >> On Mar 6, 2010, at 2:44 AM, Aaron Gray wrote: >> >> > >> > clang fails with a dynamic linking problem. >> >> What's the problem? and if you would please file a bug that
2010 Mar 06
2
[LLVMdev] Cygwin patches for 2.7
On 6 March 2010 10:47, Eric Christopher <echristo at apple.com> wrote: > > On Mar 6, 2010, at 2:44 AM, Aaron Gray wrote: > > > > > clang fails with a dynamic linking problem. > > What's the problem? and if you would please file a bug that would be > awesome :) > > thanks! > > Eric, Neither Cygwin nor MinGW support Dynamic Linking. I am getting
2009 May 15
0
[LLVMdev] [Cygwin] bug on SVN
On May 15, 2009, at 11:03 AM, Aaron Gray wrote: > I am getting a bug building Cygwin on latest SVN :- > > llvm[1]: Compiling Process.cpp for Debug build > In file included from /home/ang/git/workbench/lib/System/Process.cpp: > 29: > /home/ang/git/workbench/lib/System/Unix/Process.inc: In function > 'unsigned int g > etColumns(int)': >
2007 Oct 05
6
[LLVMdev] RFC: Tail call optimization X86
On Oct 5, 2007, at 2:42 AM, Arnold Schwaighofer wrote: > Hi Evan, > I incoporated the changes you request but to the following i have got > a question: > >> Also, moving the option >> there will allow us to change fastcc ABI (callee popping arguments) >> only when this option is on. See Chris' email: > > I am not to sure on that. because that would make
2009 Jun 11
0
[LLVMdev] Why does the x86-64 JIT emit stubs for external calls?
On Jun 10, 2009, at 12:17 PM, Jeffrey Yasskin wrote: > In X86CodeGen.cpp, the following code appears in the handler used for > CALL64pcrel32 instructions: > > // Assume undefined functions may be outside the Small > codespace. > bool NeedStub = > (Is64BitMode && > (TM.getCodeModel() == CodeModel::Large || >