search for: dinline

...al/lib/R/library' * Installing *source* package 'lpSolve' ... ** libs cc -std=gnu99 -I/usr/local/lib/R/include -I/usr/local/lib/R/include -I . -DINTEGERTIME -DPARSER_LP -DBUILDING_FOR_R -DYY_NEVER_INTERACTIVE -DUSRDLL -DCLOCKTIME -DRoleIsExternalInvEngine -DINVERSE_ACTIVE=INVERSE_LUSOL -DINLINE=static -DParanoia -I/usr/local/include -D__NO_MATH_INLINES -fpic -O2 -fno-strict-aliasing -pipe -march=prescott -c colamd.c -o colamd.o cc -std=gnu99 -I/usr/local/lib/R/include -I/usr/local/lib/R/include -I . -DINTEGERTIME -DPARSER_LP -DBUILDING_FOR_R -DYY_NEVER_INTERACTIVE -DUSRDLL -DCLOCKTIME...

On Sat, Oct 29, 2011 at 12:30:12PM -0500, Hal Finkel wrote: > Also, when using clang, I had to pass -Dinline= on the command line: > when using -emit-llvm, clang appears not to emit code for functions > declared inline. This is a bug, but I've not yet tracked it down. http://clang.llvm.org/compatibility.html#inline Thanks, -- Peter

...stuff... helper.c(3) : error C2061: syntax error : identifier ''inline'' ... some more stuff Aha. VS2005 does not like the "inline" keyword, that appears to only apply to C++ code. 3. Changed the Makefile to the following magical incantation: CFLAGS = -MD -Zi -O2b2x /Dinline=__inline /Ob /LTCG /DWIN32 Also added mt.exe -outputresource:$(DLLIB);2 -manifest $(DLLIB).manifest to the $(DLLIB): target (this is required for VS2005 to generate compatible dlls): $(DLLIB): $(DEFFILE) $(OBJS) @-$(RM) $@ $(LDSHARED) -Fe$(@) $(OBJS) $(LIBS) $(LOCAL_LIBS) $(DLDFLAGS)...

...nknown-linux-gnu-library/2.6 * Installing *source* package 'lpSolve' ... ** libs gcc -std=gnu99 -I/usr/lib64/R/include -I/usr/lib64/R/include -I . -DINTEGERTIME -DPARSER_LP -DBUILDING_FOR_R -DYY_NEVER_INTERACTIVE -DUSRDLL -DCLOCKTIME -DRoleIsExternalInvEngine -DINVERSE_ACTIVE=INVERSE_LUSOL -DINLINE=static -DParanoia -I/usr/local/include -fpic -g -O2 -c colamd.c -o colamd.o In file included from /usr/include/bits/posix1_lim.h:153, from /usr/include/limits.h:145, from /usr/lib64/gcc/x86_64-suse-linux/4.2.1/include/limits.h:122, from /usr/li...

Here are our notes on 1.1.4 testing on Windows 1. Compile Error with regular mode (FIXED_POINT undefined) at lsp.c line 104 static inline spx_word16_t spx_cos(spx_word16_t x) . VS6 does not like the inline keyword here. Removing it allows compiling. same with cb_search_sse.h line 34. 2. Compile Error with quant_lsp.c line 55. M_PI is undefined. Either it needs to be included

...lsp.c line 104 > static inline spx_word16_t spx_cos(spx_word16_t x) . VS6 does not like > the inline keyword here. Removing it allows compiling. > > same with cb_search_sse.h line 34. It seems like your compiler simply doesn't like "inline". I suggest doing a -Dinline= which is what autoconf does when it detects that the compiler doesn't understand the inline keyword. > 2. Compile Error with quant_lsp.c line 55. M_PI is undefined. Either it > needs to be included in that file or placed in a header. I'll fix that. > 3. denoise.c doesn't...

...the benchmark program by Maleki, et al. See: An Evaluation of Vectorizing Compilers - PACT'11 (http://polaris.cs.uiuc.edu/~garzaran/doc/pact11.pdf). The source of their benchmark program was retrieved from: http://polaris.cs.uiuc.edu/~maleki1/TSVC.tar.gz Also, when using clang, I had to pass -Dinline= on the command line: when using -emit-llvm, clang appears not to emit code for functions declared inline. This is a bug, but I've not yet tracked it down. There are two such small functions in the benchmark program, and the regular inliner *should* catch them anyway. Results: 0. Name of the l...

...line spx_word16_t spx_cos(spx_word16_t x) . VS6 does > not like > > the inline keyword here. Removing it allows compiling. > > > > same with cb_search_sse.h line 34. > >It seems like your compiler simply doesn't like "inline". I suggest >doing a -Dinline= which is what autoconf does when it detects that the >compiler doesn't understand the inline keyword. > > > 2. Compile Error with quant_lsp.c line 55. M_PI is undefined. Either it > > needs to be included in that file or placed in a header. > >I'll fix that. >...

...t > al. See: > An Evaluation of Vectorizing Compilers - PACT'11 > (http://polaris.cs.uiuc.edu/~garzaran/doc/pact11.pdf). The source of > their benchmark program was retrieved from: > http://polaris.cs.uiuc.edu/~maleki1/TSVC.tar.gz > > Also, when using clang, I had to pass -Dinline= on the command line: > when using -emit-llvm, clang appears not to emit code for functions > declared inline. This is a bug, but I've not yet tracked it down. There > are two such small functions in the benchmark program, and the regular > inliner *should* catch them anyway. >...

...Compilers - PACT'11 > > > (http://polaris.cs.uiuc.edu/~garzaran/doc/pact11.pdf). The source of > > > their benchmark program was retrieved from: > > > http://polaris.cs.uiuc.edu/~maleki1/TSVC.tar.gz > > > > > > Also, when using clang, I had to pass -Dinline= on the command line: > > > when using -emit-llvm, clang appears not to emit code for functions > > > declared inline. This is a bug, but I've not yet tracked it down. There > > > are two such small functions in the benchmark program, and the regular > > > in...

...valuation of Vectorizing Compilers - PACT'11 > > (http://polaris.cs.uiuc.edu/~garzaran/doc/pact11.pdf). The source of > > their benchmark program was retrieved from: > > http://polaris.cs.uiuc.edu/~maleki1/TSVC.tar.gz > > > > Also, when using clang, I had to pass -Dinline= on the command line: > > when using -emit-llvm, clang appears not to emit code for functions > > declared inline. This is a bug, but I've not yet tracked it down. There > > are two such small functions in the benchmark program, and the regular > > inliner *should* catch...