From 4da378951cb0e5a586792c3d46db5fda1b5a53e8 Mon Sep 17 00:00:00 2001
From: Mark Borgerding <mark@borgerding.net>
Date: Sun, 4 Apr 2004 22:02:02 +0000
Subject: [PATCH] minor doc changes

---
 TIPS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/TIPS b/TIPS
index b09d663..39a5fe5 100644
--- a/TIPS
+++ b/TIPS
@@ -7,6 +7,9 @@ Speed:
                 -ffast-math
                 -fomit-frame-pointer
 
+    * If the input data has no imaginary component, use the kiss_fftr code under tools/.
+      Real ffts are roughly twice as fast as complex.
+
 Reducing code size:
     * remove some of the butterflies. There are currently butterflies optimized for radices
         2,3,4,5.  It is worth mentioning that you can still use FFT sizes that contain 
@@ -14,3 +17,7 @@ Reducing code size:
         whether to keep radix 2 or 4.  If you do some work in this area, let me 
         know what you find.
 
+    * For platforms where ROM/code space is more plentiful than RAM,
+     consider creating a hardcoded kiss_fft_state. In other words, decide which 
+     FFT size(s) you want and make a structure with the correct factors and twiddles.
+