search for: cbe

...SingleSource' make[2]: Entering directory `/home/jo/Delta/llvm/projects/llvm-test/SingleSource/UnitTests' make[3]: Entering directory `/home/jo/Delta/llvm/projects/llvm-test/SingleSource/UnitTests/Vector' /home/jo/Delta/llvm/Release/bin/llc -march=c Output/build.llvm.bc -o Output/build.cbe.c -f C Writer does not know about %tmp12 = insertelement <4 x float> % tmp11, float %X.0, i32 1 ; <<4 x float>> [#uses=2] /home/jo/Delta/llvm/Release/bin/llc[0x878d8dc] [0x6] /lib32/libc.so.6(abort+0x101)[0x556f24b1] /home/jo/Delta/llvm/Release/bin/llc[0x812a0f8] mak...

...However, I get a number of failed tests: john at john-ubuntu:~/llvm/projects/test-suite$ grep FAILED\! jttestlog.txt ******************** TEST (jit) 'tls' FAILED! ******************** ******************** TEST (llc) 'initp1' FAILED! ******************** ******************** TEST (cbe) 'initp1' FAILED! ******************** ******************** TEST (cbe) 'ctor_dtor_count-2' FAILED! ******************** ******************** TEST (cbe) 'ctor_dtor_count' FAILED! ******************** ******************** TEST (cbe) 'exception_spec_test' FAILED! ******...

CBE is fairly broken everywhere AFAIK, don't worry about it. Most of the JIT failures are in tests that exercise exception handling. Not sure if that is supposed to work in your environment, it works in some JITs and not others. The LLC failures are cause for concern. On Aug 30, 2010, at 10:5...

...s are run, and and to dust off my gdb and Linux brain cells. Is there a prefered platform to run the test-suite on, where they all pass? Or is there a test output file I can compare against? Thanks. -John On Mon, Aug 30, 2010 at 11:10 AM, Dale Johannesen <dalej at apple.com> wrote: > CBE is fairly broken everywhere AFAIK, don't worry about it. > Most of the JIT failures are in tests that exercise exception handling. > Not sure if that is supposed to work in your environment, it works in some > JITs and not others. > The LLC failures are cause for concern. > >...

...moment some tests might be > broken on some platforms. Regressions are usually fixed quickly, though. > Darwin x86-{32/64} gets the most attention. > > Thanks. > > -John > > On Mon, Aug 30, 2010 at 11:10 AM, Dale Johannesen <dalej at apple.com> wrote: > >> CBE is fairly broken everywhere AFAIK, don't worry about it. >> Most of the JIT failures are in tests that exercise exception handling. >> Not sure if that is supposed to work in your environment, it works in some >> JITs and not others. >> The LLC failures are cause for co...

...at any given moment some tests might be broken on some platforms. Regressions are usually fixed quickly, though. Darwin x86-{32/64} gets the most attention. > Thanks. > > -John > > On Mon, Aug 30, 2010 at 11:10 AM, Dale Johannesen <dalej at apple.com> > wrote: > CBE is fairly broken everywhere AFAIK, don't worry about it. > Most of the JIT failures are in tests that exercise exception > handling. Not sure if that is supposed to work in your environment, > it works in some JITs and not others. > The LLC failures are cause for concern. >...

...ken on some platforms. Regressions are usually fixed quickly, though. >> Darwin x86-{32/64} gets the most attention. >> >> Thanks. >> >> -John >> >> On Mon, Aug 30, 2010 at 11:10 AM, Dale Johannesen <dalej at apple.com>wrote: >> >>> CBE is fairly broken everywhere AFAIK, don't worry about it. >>> Most of the JIT failures are in tests that exercise exception handling. >>> Not sure if that is supposed to work in your environment, it works in some >>> JITs and not others. >>> The LLC failures...

...; be broken on some platforms. Regressions are usually fixed quickly, > though. Darwin x86-{32/64} gets the most attention. > >> Thanks. >> >> -John >> >> On Mon, Aug 30, 2010 at 11:10 AM, Dale Johannesen <dalej at apple.com> >> wrote: >> CBE is fairly broken everywhere AFAIK, don't worry about it. >> Most of the JIT failures are in tests that exercise exception >> handling. Not sure if that is supposed to work in your >> environment, it works in some JITs and not others. >> The LLC failures are cause fo...

...doesn't seem easy to solve due to the unknown size of size_t (see LowerAllocations.cpp). The "void main()" problem is probably a result of this test being converted from Fortran. I'll have to dig into that some more. The missing ";" looks like a serious problem. The CBE is just generating bogus code: llvm_cbe_file_20_test_2e_f_2c__20_line_20_151_2c__20_bb66: llvm_cbe_r1380 = *(&llvm_cbe_SUM); *(&llvm_cbe__24_SUM_S94) = llvm_cbe_r1380; llvm_cbe_r1381 = *(&llvm_cbe__24_SUM_S94); return llvm_cbe_r1381 <EOF> That is, there's no semicolo...

...essions are usually fixed >> quickly, though. Darwin x86-{32/64} gets the most attention. >> >>> Thanks. >>> >>> -John >>> >>> On Mon, Aug 30, 2010 at 11:10 AM, Dale Johannesen >>> <dalej at apple.com> wrote: >>> CBE is fairly broken everywhere AFAIK, don't worry about it. >>> Most of the JIT failures are in tests that exercise exception >>> handling. Not sure if that is supposed to work in your >>> environment, it works in some JITs and not others. >>> The LLC failu...

...ource/UnitTests/Vector/SSE/sse.expandfft TEST-FAIL: jit /SingleSource/UnitTests/Vector/SSE/sse.expandfft TEST-FAIL: llc /SingleSource/UnitTests/Vector/SSE/sse.isamax TEST-FAIL: jit /SingleSource/UnitTests/Vector/SSE/sse.isamax TEST-FAIL: jit /SingleSource/UnitTests/Vector/SSE/sse.stepfft TEST-FAIL: cbe /SingleSource/UnitTests/Vector/build2 TEST-FAIL: cbe /SingleSource/UnitTests/Vector/build TEST-FAIL: cbe /SingleSource/UnitTests/Vector/divides TEST-FAIL: jit /SingleSource/UnitTests/Vector/multiplies TEST-FAIL: cbe /SingleSource/UnitTests/Vector/multiplies TEST-FAIL: cbe /SingleSource/UnitTests/Ve...

...haven't finished this, but I thought the following might be useful for other people that are testing the release on Linux. Each group of failing tests below is followed by a comment about why its failing. llc /MultiSource/Applications/oggenc/oggenc jit /MultiSource/Applications/oggenc/oggenc cbe /MultiSource/Applications/oggenc/oggenc ^^ no idea what's causing these jit /MultiSource/Applications/JM/ldecod/ldecod ^^ weird jit codegen problem produces wrong FP output, PR963 llc /MultiSource/Applications/JM/lencod/lencod jit /MultiSource/Applications/JM/lencod/lencod cbe /MultiSourc...

On Aug 25, 2010, at 12:45 PM, John Thompson wrote: > Hi, > > I'm looking for some feedback on the changes represented in the > attached patches, which I'll describe below. > > I'm sending this to both the LLVM and Clang list because it affects > both, though the main focus here is LLVM. > Basically, I've partially implemented some changes for choosing

...ough (see previous email). Sparc testing results: make check: # of expected passes 1189 # of expected failures 34 Regressions Single Source: None New Failures Single Source (new tests): 2005-05-12-Int64ToFP: llc,jit Regressions MultiSource: Applications/d/make_dparser: llc, cbe, jit Applications/hexxagon/hexxagon: llc, cbe, jit Benchmarks/MallocBench/gs/gs: llc, cbe Benchmarks/Prolangs-C/cdecl/cdecl: llc, cbe, jit Benchmarks/Prolangs-C/football/football: cbe Benchmarks/Prolangs-C/gnugo/gnugo: llc, cbe, jit Benchmarks/Prolangs-C/agrep/agrep: llc Benchmarks/Prolangs-C/fixou...

Hi, I'm running into some strange errors with the CBE. I've narrowed the problem down to a very simple CPP program: main.cpp: -------------------------------------------------------------------------------- #include <string> static std::string hello("Hello world!"); int main() { return 0; } --------------------------------...

...41 LLVM-TEST NIGHTLY WITH LLVM-GCC3 (FAIL) * The following tests fail: TEST-FAIL: compile /SingleSource/UnitTests/2006-01-23-InitializedBitField TEST-FAIL: llc /SingleSource/UnitTests/2006-01-23-InitializedBitField TEST-FAIL: jit /SingleSource/UnitTests/2006-01-23-InitializedBitField TEST-FAIL: cbe /SingleSource/UnitTests/2006-01-23-InitializedBitField TEST-FAIL: compile /SingleSource/UnitTests/2006-01-23-UnionInit TEST-FAIL: llc /SingleSource/UnitTests/2006-01-23-UnionInit TEST-FAIL: jit /SingleSource/UnitTests/2006-01-23-UnionInit TEST-FAIL: cbe /SingleSource/UnitTests/2006-01-23-UnionInit...

On Wednesday 16 July 2008 10:12, David Greene wrote: > I'm having some trouble using bugpoint with newer version of gcc (bugpoint > debug output below). I was using gcc 4.1.2. When I try 3.2.3 I get: bugpoint-test-program.bc.cbe.c:237: warning: conflicting types for built-in function `memcpy' bugpoint-test-program.bc.cbe.c: In function `main': bugpoint-test-program.bc.cbe.c:581: no vector mode with the size and type specified could be found and a bunch more vector errors. So I'm in a bit of a pickle. Does...

LLVMers, The LLVM 1.9 Prerelease is available for testing: http://llvm.org/prereleases/1.9/ If anyone can spare some time, please download the appropriate tarballs for your platform and test the release (at least with make check). I'd also appreciate any documentation reviews. Please note that llvm-gcc3 on x86 may not have a clean dejagnu run. You should see one XPASS for

...8 10:31, David Greene wrote: > On Wednesday 16 July 2008 10:12, David Greene wrote: > > I'm having some trouble using bugpoint with newer version of gcc > > (bugpoint debug output below). > > I was using gcc 4.1.2. When I try 3.2.3 I get: > > bugpoint-test-program.bc.cbe.c:237: warning: conflicting types for built-in > function `memcpy' > bugpoint-test-program.bc.cbe.c: In function `main': > bugpoint-test-program.bc.cbe.c:581: no vector mode with the size and type > specified could be found > > and a bunch more vector errors. > > So...

Hi, I'm looking for some feedback on the changes represented in the attached patches, which I'll describe below. I'm sending this to both the LLVM and Clang list because it affects both, though the main focus here is LLVM. Basically, I've partially implemented some changes for choosing multiple alternative constraints largely on the LLVM side. The Clang change is to output the