On Mon, 18 Oct 2010 17:12:44 -0500 René Berber <rber...@prodigy.net.mx> wrote:
> On 10/18/2010 4:08 PM, René Berber wrote: > > On 10/18/2010 3:42 PM, Török Edwin wrote: > > > >> For me it is (UltraSPARC-T2 @1165 MHz): > >> official signatures: Time: 22.255 sec (0 m 22 s) > >> official + sanesecurity: Time: 90.417 sec (1 m 30 s) > >> > >> That is with gcc 3.4.6. > >> With gcc 4.4.3 I get 74s load time. > >> With Sun studio 12 it takes 241s, (the default must be no > >> optimization probably). > >> > >> You may try to get more speed by using -mcpu switches. > >> Manpage says "By default (unless configured otherwise) GCC > >> generates code for the V7 variant of the SPARC architecture". > >> > >> So you could try -mcpu=niagara2 for example. You can also try -O3 > >> instead of -O2 (but expect more compiler bugs). > >> > >> So try this (adjust -mcpu to the CPU you really have, see manpage > >> for possible choices). > >> ./configure CFLAGS="-mcpu=niagara2 -mtune=niagara2 -O3" > >> See if it works, if not replace O3 with O2 and try again. > > With -O3 it fails one of the tests: > > PASS: check_clamav > PASS: check_freshclam.sh > PASS: check_sigtool.sh > SKIP: check_unit_vg.sh > PASS: check1_clamscan.sh > PASS: check2_clamd.sh > FAIL: check3_clamd.sh > PASS: check4_clamd.sh > SKIP: check5_clamd_vg.sh > SKIP: check6_clamd_vg.sh > SKIP: check7_clamd_hg.sh > SKIP: check8_clamd_hg.sh > > Same thing happens with -O2. unit-tests/test-suite.log should have more details on how it fails, can you post relevant bits from that file (or open a bug and attach it). Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
