> [2] If you're using gcc, and you're creating C code for constant float > tables that you want compiled fast, turn the data into hexadecimal > strings: > > char foo[5] = "\x00\x00\xa0\x41"; Won't this break it for both Sun & PPC (and any other BE machine) ? > compiles quicker than > > float foo[1] = { 0.39485}; - that is I think it's a byte ordering problem - not an embedded 0 problem (but maybe I'm not awake yet :-) [or maybe you re-reverse it at run-time] Iain.
- [linux-audio-dev] sfront 0.65 09/07/00 John Lazzaro
- Re: [linux-audio-dev] sfront 0.65 09/07/00 Paul Winkler
- Re: [linux-audio-dev] sfront 0.65 09/07/00 Iain Sandoe
- Re: [linux-audio-dev] sfront 0.65 09/07/00 John Lazzaro
- Re: [linux-audio-dev] sfront 0.65 09/07/00 Paul Barton-Davis
- Re: [linux-audio-dev] sfront 0.65 09/07/00 Iain Sandoe
- Re: [linux-audio-dev] sfront 0.65 09/07/00 John Lazzaro
- Re: [linux-audio-dev] sfront 0.65 09/07/00 John Lazzaro