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
http://lists.cs.uiuc.edu/mai
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 b
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
> +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.
___
l
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
> fu
>
> 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
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 y
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
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 l
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
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. T
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.
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 comma
> 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 ou
14 matches
Mail list logo
