Changes in directory llvm/test/lib:
llvm.exp updated: 1.23 - 1.24
---
Log message:
Fix typo.
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/test/lib/llvm.exp
diff -u llvm/test/lib/llvm.exp:1.23 llvm/test/lib/llvm.exp:1.24
Hi Reid,
+ if { [ string first $lang $llvmgcc_langs ] = 0 } {
won't c match c,c++,objc and objc++; and c++ match both c++ and objc++,
etc?
Best wishes,
Duncan.
___
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
Changes in directory llvm/test/lib:
llvm.exp updated: 1.22 - 1.23
---
Log message:
Dan is right, using string first would produce false positives. So,
devolve the check to a comparison against each component in the string.
Fortunately there isn't many of them.
---
Diffs of the changes: (+9
Changes in directory llvm/test/lib:
llvm.exp updated: 1.21 - 1.22
---
Log message:
Fix the comparison of language names to accept any characters by using
string first instead of regexp match. This helps C++ tests get executed.
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files
+catch { set file_h [ open /tmp/llvm_obj_check.m w] }
+set R [ catch { exec $llvmgcc -c /tmp/llvm_obj_check.m -o /dev/null
/tmp/llvm_obj_check.out } ]
Will using /tmp and /dev/null work properly under Windows?
Ciao,
Duncan.
___
Changes in directory llvm/test/lib:
llvm.exp updated: 1.16 - 1.17
---
Log message:
Put failure information on a separate line. Hopefully this unbreaks the
nightly tester which expects the FAIL: line to only have the test name on
it.
---
Diffs of the changes: (+4 -4)
llvm.exp |8
The only way to run the tests under Windows is to use cygwin, using an
LLVM built with cygwin/mingw. Windows does not have /tmp (unless you
create it yourself) and it does not have /dev/null (unless cygwin
emulates it somehow). I only build LLVM on Windows with Visual Studio,
so someone else
Changes in directory llvm/test/lib:
llvm.exp updated: 1.17 - 1.18
---
Log message:
Always print the same PR information in the same location (just after
the test name) in all cases (PASS, XPASS, FAIL, XFAIL). This makes the
output consistent and more amenable to parsing by nightly test.
---
On Sat, 2007-04-21 at 11:52 -0700, Jeff Cohen wrote:
The only way to run the tests under Windows is to use cygwin, using an
LLVM built with cygwin/mingw. Windows does not have /tmp (unless you
create it yourself) and it does not have /dev/null (unless cygwin
emulates it somehow). I only
Changes in directory llvm/test/lib:
llvm.exp updated: 1.18 - 1.19
---
Log message:
Test if the compiler supports Ada, and enable Ada tests if so. While I was
there, delete a temporary file the objc test forgot to delete.
---
Diffs of the changes: (+17 -0)
llvm.exp | 17
Changes in directory llvm/test/lib:
llvm.exp updated: 1.19 - 1.20
---
Log message:
Add the llvm_supports_target function.
---
Diffs of the changes: (+9 -0)
llvm.exp |9 +
1 files changed, 9 insertions(+)
Index: llvm/test/lib/llvm.exp
diff -u llvm/test/lib/llvm.exp:1.19
Changes in directory llvm/test/lib:
llvm.exp updated: 1.20 - 1.21
---
Log message:
Replace llvm_gcc_supports_ada and llvm_gcc_supports_objc with just a single
llvm_gcc_supports function that takes the language as an argument. Base that
function on the new LLVMGCC_LANGS configured variable so
Changes in directory llvm/test/lib:
llvm.exp updated: 1.13 - 1.14
---
Log message:
Change ne into !=.
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/test/lib/llvm.exp
diff -u llvm/test/lib/llvm.exp:1.13
Changes in directory llvm/test/lib:
llvm.exp updated: 1.14 - 1.15
---
Log message:
Spelling fix.
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/test/lib/llvm.exp
diff -u llvm/test/lib/llvm.exp:1.14
Changes in directory llvm/test/lib:
llvm.exp updated: 1.7 - 1.8
---
Log message:
Abandone the entire test case on the first error.
---
Diffs of the changes: (+7 -4)
llvm.exp | 11 +++
1 files changed, 7 insertions(+), 4 deletions(-)
Index: llvm/test/lib/llvm.exp
diff -u
Changes in directory llvm/test/lib:
llvm.exp updated: 1.8 - 1.9
---
Log message:
No, don't cancel all remaining tests, just the one that failed!
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/test/lib/llvm.exp
diff -u
Changes in directory llvm/test/lib:
llvm.exp updated: 1.9 - 1.10
---
Log message:
Two improvements:
1. Only read the first 1024 bytes of the file. The RUN: lines should all be
within that amount of space. This keeps I/O costs down when reading
very large files.
2. Print PR numbers with
1. Only read the first 1024 bytes of the file. The RUN: lines
should all be
within that amount of space. This keeps I/O costs down when
reading
very large files.
If this is such a big deal, why not run command line 'grep RUN:' over
the file first, and have tcl process the output
On Sun, 2007-04-15 at 11:04 -0700, Chris Lattner wrote:
1. Only read the first 1024 bytes of the file. The RUN: lines
should all be
within that amount of space. This keeps I/O costs down when
reading
very large files.
If this is such a big deal, why not run command line
On Apr 15, 2007, at 11:13 AM, Reid Spencer wrote:
On Sun, 2007-04-15 at 11:04 -0700, Chris Lattner wrote:
1. Only read the first 1024 bytes of the file. The RUN: lines
should all be
within that amount of space. This keeps I/O costs down when
reading
very large files.
If this is
On Sun, 2007-04-15 at 11:18 -0700, Chris Lattner wrote:
On Apr 15, 2007, at 11:13 AM, Reid Spencer wrote:
On Sun, 2007-04-15 at 11:04 -0700, Chris Lattner wrote:
1. Only read the first 1024 bytes of the file. The RUN: lines
should all be
within that amount of space. This keeps I/O
Changes in directory llvm/test/lib:
llvm.exp updated: 1.10 - 1.11
---
Log message:
Allow lines that have \ and end in \ to be recognized as ending in \
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/test/lib/llvm.exp
diff
On Apr 15, 2007, at 11:37 AM, Reid Spencer wrote:
If this is such a big deal, why not run command line 'grep RUN:'
over
the file first, and have tcl process the output of that?
That doesn't save you the I/O.
Have you timed how long it takes to grep through a 1M file?
I'm not claiming
I will investigate tomorrow, but I think the CodeGen/ARM/long.ll test
is failing because its header has more than 1024 bytes.
Lauro
2007/4/15, Chris Lattner [EMAIL PROTECTED]:
On Apr 15, 2007, at 11:37 AM, Reid Spencer wrote:
If this is such a big deal, why not run command line 'grep
On Sun, 2007-04-15 at 16:55 -0300, Lauro Ramos Venancio wrote:
I will investigate tomorrow, but I think the CodeGen/ARM/long.ll test
is failing because its header has more than 1024 bytes.
Yup, fixed.
Lauro
2007/4/15, Chris Lattner [EMAIL PROTECTED]:
On Apr 15, 2007, at 11:37 AM,
On Sun, 2007-04-15 at 12:37 -0700, Chris Lattner wrote:
On Apr 15, 2007, at 11:37 AM, Reid Spencer wrote:
If this is such a big deal, why not run command line 'grep RUN:'
over
the file first, and have tcl process the output of that?
That doesn't save you the I/O.
Have you
Changes in directory llvm/test/lib:
llvm.exp updated: 1.11 - 1.12
---
Log message:
Some tests have really long RUN line sets. Read the first 4096 bytes instead
of 1024.
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index:
Changes in directory llvm/test/lib:
llvm.exp updated: 1.12 - 1.13
---
Log message:
Two changes:
1. Don't bother truncating reading of the file. It doesn't save that much
time and we should support putting RUN lines anywhere in the file. For
example, someone might want to put the grep
That doesn't save you the I/O.
Have you timed how long it takes to grep through a 1M file?
I'm not claiming this is a huge performance win :)
Then why bother?
Because its a small performance win on the huge files.
Enough to be worthwhile? We don't want huge files in llvm/test.
-Chris
On Apr 15, 2007, at 1:44 PM, Reid Spencer wrote:
Two changes:
1. Don't bother truncating reading of the file. It doesn't save
that much
time and we should support putting RUN lines anywhere in the
file. For
example, someone might want to put the grep match before each
function
Changes in directory llvm/test/lib:
llvm.exp added (r1.1)
---
Log message:
Initial version of a re-write of llvm-runtest that doesn't write the
tests to a script file but executes each line individually and catches
errors on each line too.
---
Diffs of the changes: (+159 -0)
llvm.exp |
Changes in directory llvm/test/lib:
llvm.exp updated: 1.1 - 1.2
---
Log message:
Add the line number where the script failed to the error output.
---
Diffs of the changes: (+6 -4)
llvm.exp | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
Index: llvm/test/lib/llvm.exp
Changes in directory llvm/test/lib:
llvm.exp updated: 1.2 - 1.3
---
Log message:
Print full errorInfo when a failure occurs.
---
Diffs of the changes: (+1 -1)
llvm.exp |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/test/lib/llvm.exp
diff -u
Changes in directory llvm/test/lib:
llvm.exp updated: 1.3 - 1.4
---
Log message:
1. Don't generate redundant copy of stderr
2. Only match \ at the *end* of a line.
---
Diffs of the changes: (+2 -2)
llvm.exp |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Index:
Changes in directory llvm/test/lib:
llvm.exp updated: 1.4 - 1.5
---
Log message:
For PR1319: http://llvm.org/PR1319 :
More improvements:
1. Using ::errorInfo wasn't such a hot idea. Go back to just printing the
offending line of code and the stderr output. This is sufficient and
not
Changes in directory llvm/test/lib:
llvm.exp updated: 1.5 - 1.6
---
Log message:
Changes to fix problems with make check. Apparently you can redefine
functions and Tcl's just tickled with that. The fix is to give the new
test system a different interface function name.
---
Diffs of the
Changes in directory llvm/test/lib:
llvm.exp updated: 1.6 - 1.7
---
Log message:
Allow replacement of %% with %
---
Diffs of the changes: (+2 -0)
llvm.exp |2 ++
1 files changed, 2 insertions(+)
Index: llvm/test/lib/llvm.exp
diff -u llvm/test/lib/llvm.exp:1.6
37 matches
Mail list logo
