Displaying 5 results from an estimated 5 matches for "mei16v2".
2008 Jan 30
0
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
Devang has fixed the bug. I've added ClamAV to the testsuite.
Thanks!
Evan
On Jan 13, 2008, at 7:33 PM, Evan Cheng wrote:
> I've filed
> http://www.llvm.org/bugs/show_bug.cgi?id=1912
> for the optimizer bug.
>
> Evan
>
> On Jan 10, 2008, at 11:28 AM, Evan Cheng wrote:
>
>> Hi,
>>
>> We are getting closer.
>>
>> 1. In Makefile, all
2008 Jan 14
2
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
I've filed
http://www.llvm.org/bugs/show_bug.cgi?id=1912
for the optimizer bug.
Evan
On Jan 10, 2008, at 11:28 AM, Evan Cheng wrote:
> Hi,
>
> We are getting closer.
>
> 1. In Makefile, all the references to CFLAGS should be CPPFLAGS
> instead.
> 2. filterdiff.sh uses sed -re. This causes a problem on Mac OS X where
> -E means using extended regular expression, not
2008 Jan 08
2
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
...clude/shared:
> cdiff.h
> cfgparser.h
> getopt.h
> misc.h
> network.h
> options.h
> output.h
> sha256.h
>
> ./inputs:
> clam.cab
> clamdoc.pdf
> clam.exe
> clam.exe.bz2
> clam-v2.rar
> clam-v3.rar
> clam.zip
> dbdir
> docs
> large.pcm
> mei16v2.m2v
> README
> rtf-test
> tune
>
> ./inputs/rtf-test:
> Doc11.rtf
> Doc1.rtf
> Doc22.rtf
> Doc2.rtf
> doc3.rtf
> docCLAMexe.rtf
> rtf1.rtf
> rtf-novirus.rtf
>
> ./Output:
> clamscan.cbe
> clamscan.cbe.c
> clamscan_clamscan.bc
> clamscan_clams...
2007 Dec 18
0
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
Chris Lattner wrote:
> One way to do this is to add a "cut down" version of the app to the
> test suite.
I disabled optional features in clamav-config.h
>
>> 2. GPL license. Chris?
>
> Any open source license that allows unrestricted redistribution is
> fine in llvm-test
Ok, I have created a script that automatically checks out ClamAV
0.92-stable source code
2007 Dec 18
3
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
On Mon, 17 Dec 2007, Evan Cheng wrote:
> We always welcome more tests. But it looks like there are two issues
> here.
>
> 1. The autoconf requirement. Is it possible to get one configuration
> working without the need for autoconf?
One way to do this is to add a "cut down" version of the app to the test
suite.
> 2. GPL license. Chris?
Any open source license that