The _fast integer types provide no realworld benefits, but may introduce
portability issues and are just plain ugly.
---
 libmpeg2/idct_alpha.c |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/libmpeg2/idct_alpha.c b/libmpeg2/idct_alpha.c
index 8e94219..490b659 100644
--- a/libmpeg2/idct_alpha.c
+++ b/libmpeg2/idct_alpha.c
@@ -53,7 +53,7 @@ do {                                  \
 #else
 #define BUTTERFLY(t0,t1,W0,W1,d0,d1)   \
 do {                                   \
-    int_fast32_t tmp = W0 * (d0 + d1); \
+    int32_t tmp = W0 * (d0 + d1);      \
     t0 = tmp + (W1 - W0) * d1;         \
     t1 = tmp - (W1 + W0) * d0;         \
 } while (0)
@@ -62,9 +62,9 @@ do {                                  \
 static inline void idct_row (int16_t * const block)
 {
     uint64_t l, r;
-    int_fast32_t d0, d1, d2, d3;
-    int_fast32_t a0, a1, a2, a3, b0, b1, b2, b3;
-    int_fast32_t t0, t1, t2, t3;
+    int32_t d0, d1, d2, d3;
+    int32_t a0, a1, a2, a3, b0, b1, b2, b3;
+    int32_t t0, t1, t2, t3;
 
     l = ldq (block);
     r = ldq (block + 4);
@@ -118,9 +118,9 @@ static inline void idct_row (int16_t * const block)
 
 static inline void idct_col (int16_t * const block)
 {
-    int_fast32_t d0, d1, d2, d3;
-    int_fast32_t a0, a1, a2, a3, b0, b1, b2, b3;
-    int_fast32_t t0, t1, t2, t3;
+    int32_t d0, d1, d2, d3;
+    int32_t a0, a1, a2, a3, b0, b1, b2, b3;
+    int32_t t0, t1, t2, t3;
 
     d0 = (block[8*0] << 11) + 65536;
     d1 = block[8*1];
-- 
1.5.6.5


------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Libmpeg2-devel mailing list
Libmpeg2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmpeg2-devel

Reply via email to