search for: fsingle

...et the bottom of why we're crashing with double floating point literal. It seems the fpu in question (fpv4-sp-d16) only supports 32 bit operations so this is somehow getting passed to a software wrapper and crashing there. But to be fair this was crashing in gcc too which is why we added the -fsingle-precision-constant flag since we didn't care about the precision of the constants and we're using floats everywhere anyway for performance. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150715/099d1...

Hi All, Clang lacks support for the -fsingle-precision-constant flag. Are there specific reasons for this or is it just waiting to be implemented? This flag is especially important in the embedded world. From http://processors.wiki.ti.com/index.php/Floating_Point_Optimization#float_vs._double_vs._long_double : *Once all of your data is de...

...----------------------------------------------------------------------------------------------------------------- gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -g -I/root/local/asterisk/asterisk/include -D_REENTRAN_SOURCE -O3 -ffast-math -funroll-all-loops -fprefetch-loop-arrays -fsingle-precision-constant -DCRYPTO -DAPP_CONFERUG -c -o app_conference.o app_conference.c gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -g -I/root/local/asterisk/asterisk/include -D_REENTRAN_SOURCE -O3 -ffast-math -funroll-all-loops -fprefetch-loop-arrays -fsingle-precision-constant...

...o cli.o libspeex/preprocess.o libspeex/misc.o libspeex/smallft.o [root@centos app_conference]# make gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -g -I/root/sources/asterisk02/asterisk-1.2.8/include -D_REENTRANT -D_GNU_SOURCE -O3 -ffast-math -funroll-all-loops -fprefetch-loop-arrays -fsingle-precision-constant -DCRYPTO -march=k8 -fPIC -DAPP_CONFERENCE_DEBUG -Ilibspeex -DSILDET=2 -c -o app_conference.o app_conference.c gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -g -I/root/sources/asterisk02/asterisk-1.2.8/include -D_REENTRANT -D_GNU_SOURCE -O3 -ffast-math -funroll-a...

On Fri, Apr 02, 2004 at 12:33:13AM -0500, Jean-Marc Valin wrote: > Do you have any sample code for that? Also, how do you tell autoconf to > append '-msse' without running into problems when CFLAGS is not set (and > usually defaults to -g -O2, but not always). Example patch attached. It only tries if the use passes --enable-sse; testing by target arch as Aron suggested is

...ot;-lfasttime" #LD_PRELOAD_64=/usr/lib/amd64/libmtmalloc.so LDFLAGS="-L/opt/yp/lib -R/opt/yp/lib -L/usr/sfw/lib/64 -R/usr/sfw/lib/ 64 -L/usr/ sfw/lib -R/usr/sfw/lib -L/usr/lib/64 -R/usr/lib/64 -L/usr/lib -R/usr/ lib" # Compiler Flags #CFLAGS="-m64 -xarch=sse2 -fns -fsimple=2 -fsingle -nofstore - xalias_level=basic -xbuiltin=%all -xdepend -xlibmil -xlibmopt -xO5 -xregs=frameptr -mt - lpthread" CXX=CC #CXXFLAGS="-m64 -xarch=sse2 -fns -fsimple=2 -fsingle -nofstore - xalias_level=bas ic -xbuiltin=%all -xdepend -xlibmil -xlibmopt -xO5 -xregs=frameptr -mt -lpthread &quot...

On Mon, 2005-02-28 at 19:42 -0500, Jean-Marc Valin wrote: > > jean-marc: i think we can remove spx_sig_t *orig. > > but am not sure about exc2Buf. is it for extension? > > orig is already removed in SVN (which you should probably use). As for > exc2, it can be removed, but I'm not sure if you can just use exc > instead (maybe yes). > when removing "spx_sig_t

...ions.html#Optimize-Options> > > -ffp-contract=style > -ffast-math > -fno-math-errno > -funsafe-math-optimizations > -fassociative-math > -freciprocal-math > -ffinite-math-only > -fno-signed-zeros > -fno-trapping-math > -frounding-math > -fsignaling-nans > -fsingle-precision-constant > > etc, and the relevant negations of these options. We can't predict how customers will choose to chain these together, so I think the LLVM optimizer and backend designs should accommodate all possibilities derived from those clang flags. This includes (because I'...

...ly be very close, if you can do it. I did a bunch of tests of encoder performance (on an Athlon XP 1700+) a while back, and found that, for 8kbps CBR complexity 1, I got: (encode/decode speed) basic compile: 29.2x / 168x -O3 -ffast-math -funroll-all-loops -march=pentium3 -fprefetch-loop-arrays -fsingle-precision-constant: 53.4x / 361x With -msse: 65x/386x The actual numbers don't matter much, but it does mean that encoding is almost 6x as expensive as decoding, so expect that you're going to use 60-90% of your CPU for speex encode.. -SteveK -------------- next part -------------...

...ons.html# > Optimize-Options > > -ffp-contract=style > -ffast-math > -fno-math-errno > -funsafe-math-optimizations > -fassociative-math > -freciprocal-math > -ffinite-math-only > -fno-signed-zeros > -fno-trapping-math > -frounding-math > -fsignaling-nans > -fsingle-precision-constant > > etc, and the relevant negations of these options. We can't predict how > customers will choose to chain these together, so I think the LLVM > optimizer and backend designs should accommodate all possibilities derived > from those clang flags. This includes...

When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be added to the CFLAGS in libspeex/Makefile. GCC 3.1.1 added a new option "-msse" (see http://gcc.gnu.org/gcc-3.1/changes.html , specifically under "New Targets and Target Specific Improvements") to enable SSE instructions within the compiler's output (for appropriate architectures). Compiling speex on

On 17.11.2016 09:51, Ristow, Warren wrote: > Those are all good points. Your reassociation point in the context of > inlining is particularly interesting. > > > > FWIW, we also have a case where a customer wants '-fno-associative-math' > to suppress reassociation under '-ffastmath'. It would take me a while > to find the specifics of the issue, but it was

...---------- Specify the floating point constant with single precision. The patch changes the similar line A to B. A: if (analysis->activity<.4) B: if (analysis->activity<.4f) For ARM Cortex-M4F, it has only a *single precision* (float) FPU, and Keil MDK compiler cannot recognize "-fsingle-precision-constant". The compiler gives the following warning to the line A warning: #1035-d: single-precision operand implicitly converted to double-precision More details, refer to: https://mcuoneclipse.com/2019/03/29/be-aware-floating-point-operations-on-arm-cortex-m4f/ diff -Naup...