From 091e54c0f13d72307be568daabe630bb3463393c Mon Sep 17 00:00:00 2001 From: Dan Stowell Date: Mon, 19 Mar 2007 15:06:55 +0000 Subject: xtract_mfcc(): Slightly different way of limiting to XTRACT_LOG_LIMIT. It's the same in theory, but saves on one assignment operation. But the real reason I did it was because my compiler (gcc 4.0.1, Apple intel edition) was getting it wrong (presumably during some optimisation). It does save on the assignment though. --- src/vector.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'src') diff --git a/src/vector.c b/src/vector.c index 75404f0..5e5057a 100644 --- a/src/vector.c +++ b/src/vector.c @@ -163,8 +163,7 @@ int xtract_mfcc(const float *data, const int N, const void *argv, float *result) for(n = 0; n < N; n++){ result[filter] += input[n] * f->filters[filter][n]; } - if(result[filter] < XTRACT_LOG_LIMIT) result[filter] = XTRACT_LOG_LIMIT; - result[filter] = log(result[filter]); + result[filter] = log(result[filter] < XTRACT_LOG_LIMIT ? XTRACT_LOG_LIMIT : result[filter]); } for(n = filter + 1; n < N; n++) result[n] = 0; -- cgit v1.2.3