From: David B. <da...@pa...> - 2009-10-13 11:24:59
|
On Tuesday 13 October 2009, Øyvind Harboe wrote: > I'm not crazy about the memset() w.r.t. performance of inner loops. I wouldn't call those "inner loops"; or consider *knowing* the code is correct to ever be an issue. And in any case, GCC tends to use a builtin, which gives *VERY* tight code. Loop runs inside of one cacheline, etc. p.s. gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../src/helper -I../../src/jtag -I../../src/xsvf -I/usr/local/include -Wall -Wstrict-prototypes -Wformat-security -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Werror -MT arm11.lo -MD -MP -MF .deps/arm11.Tpo -c arm11.c -o arm11.o cc1: warnings being treated as errors arm11_dbgtap.c: In function ‘arm11_run_instr_data_to_core_noack’: arm11_dbgtap.c:593: warning: format ‘%d’ expects type ‘int’, but argument 6 has type ‘size_t’ make[3]: *** [arm11_dbgtap.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... |