search for: core2

...]: Nothing to be done for `svnonly'. installing C headers make[2]: Nothing to be done for `all'. make[2]: `libRblas.dll.a' is up to date. make[5]: Nothing to be done for `svnonly'. installing C headers make --no-print-directory -C ../extra/intl CFLAGS='-O3 -Wall -pedantic -mtune=core2' -f Makefile.win make --no-print-directory -C ../appl CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../nmath CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win mak...

...]: Nothing to be done for `svnonly'. installing C headers make[2]: Nothing to be done for `all'. make[2]: `libRblas.dll.a' is up to date. make[5]: Nothing to be done for `svnonly'. installing C headers make --no-print-directory -C ../extra/intl CFLAGS='-O3 -Wall -pedantic -mtune=core2' -f Makefile.win make --no-print-directory -C ../appl CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../nmath CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win mak...

...llvm is used by mesa package, llvm will produces binary code with SSE4 instructions, which is not compatible with pentium dual core, because this CPU doesn't support SSE4 instructions ( bad cpu opcodes ), with llvm 3.6.2 this bug doesn't occur because pentium dual core was treated as "core2" cpu, which is the good behaviour, the llvm git commit who has introduced this bug is : cd83d5b5071f072882ad06cc4b904b2d27d1e54a https://github.com/llvm-mirror/llvm/commit/cd83d5b5071f072882ad06cc4b904b2d27d1e54a this faulty commit has deleted a crucial test about SSE4 for CPU family 6 mod...

...2.9 (with the llvm-gcc front end) to compile and run the SPEC CPU2006 benchmarks on x86. We are compiling and running the benchmarks on a an Intel Xeon E5540 processor running Ubuntu 10.10 (64-bit version). For the native x86-64 target, we are using the following command-line arguments: -O3 -march=core2 -mtune=core2 and are getting compile-time errors on the gamess and tonto benchmarks. For the native x86-32 target, we are using the following command-line arguments: -O3 -march=core2 -mtune=core2 -m32 and are getting compile-time errors on gamess and tonto as well as run-time errors on gcc, cactu...

...making Rembedded.d from Rembedded.c making dynload.d from dynload.c making system.d from system.c making sys-unix.d from sys-unix.c making sys-std.d from sys-std.c making X11.d from X11.c clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -Wall -mtune=core2 -g -O2 -c Rembedded.c -o Rembedded.o clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -Wall -mtune=core2 -g -O2 -c dynload.c -o dynload.o clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -Wall -mtune...

...]: Nothing to be done for `svnonly'. installing C headers make[2]: Nothing to be done for `all'. make[2]: `libRblas.dll.a' is up to date. make[5]: Nothing to be done for `svnonly'. installing C headers make --no-print-directory -C ../extra/intl CFLAGS='-O3 -Wall -pedantic -mtune=core2' -f Makefile.win make --no-print-directory -C ../appl CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../nmath CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win mak...

...util.c src/C/pagerank.c src/C/hierarchical.c src/C/factor_model_multicontext.c src/C/factor_model_util2.cpp -o lib/c_funcs.so make[1]: Entering directory `/cygdrive/c/Users/yi/Desktop/Yi/Latent Factor models' g++ -I"C:/PROGRA~1/R/R-215~1.1/include" -DNDEBUG -O2 -Wall -mtune=core2 -c src/C/factor_model_util2.cpp -o src/C/factor_model_util2.o src/C/factor_model_util2.cpp:1: error: bad value (core2) for -mtune= switch C:/PROGRA~1/R/R-215~1.1/etc/i386/Makeconf:179: recipe for target `src/C/factor_model_util2.o' failed make[1]: *** [src/C/factor_model_util2.o] Error 1 make[1...

...number of physical registers to study register pressure reduction under more stringent constraints (as part of an academic research project). However, the observation that I am trying to communicate in this posting may not be related to register pressure. The observation is that using the -march=core2 and -mtune=core2 options makes a significant positive difference in x86-32 mode (that is, with the -m32 option), while it does not make any significant difference in the x86-64 mode (without the -m32 option). My hypothesis is that the LLVM back end is making some good target-specific optimizations...

...d.d from dynload.c > > making system.d from system.c > > making sys-unix.d from sys-unix.c > > making sys-std.d from sys-std.c > > making X11.d from X11.c > > clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -Wall -mtune=core2 -g -O2 -c Rembedded.c -o Rembedded.o > > clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -Wall -mtune=core2 -g -O2 -c dynload.c -o dynload.o > > clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H...

...isters to study register pressure > reduction under more stringent constraints (as part of an academic research > project). However, the observation that I am trying to communicate in this > posting may not be related to register pressure. > > The observation is that using the -march=core2 and -mtune=core2 options > makes a significant positive difference in x86-32 mode (that is, with the > -m32 option), while it does not make any significant difference in the > x86-64 mode (without the -m32 option). > This is exactly the phenomenon we were describing to you. With no ...

.../i386/open.exe > mkdir -p ../../../bin > cp Rfe.exe ../../../bin/R.exe > mkdir -p ../../../bin > cp Rfe.exe ../../../bin/Rscript.exe > make[1]: `COPYRIGHTS' is up to date. > make --no-print-directory -C ../modules -f Makefile.win \ > CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' > gcc -std=gnu99 -shared -s -o ../../../bin/i386/Rlapack.dll dlamch.o > dlapack.o cmplx.o init_win.o Rlapackrc.o -L../../../bin/i386 -lR > -lRblas -lgfortran > cp lapack.dll ../../../modules/i386/lapack.dll > > and there is (obviously) read...

...dded.c > making dynload.d from dynload.c > making system.d from system.c > making sys-unix.d from sys-unix.c > making sys-std.d from sys-std.c > making X11.d from X11.c > clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -Wall -mtune=core2 -g -O2 -c Rembedded.c -o Rembedded.o > clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -Wall -mtune=core2 -g -O2 -c dynload.c -o dynload.o > clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fPIC -W...

The old CPU_CLK_UNHALTED performance counter no longer runs on Core or Core2 CPUs. Use the new CPU_CLK_UNHALTED.CORE_P one. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

..../bin/i386 cp open.exe ../../../bin/i386/open.exe mkdir -p ../../../bin cp Rfe.exe ../../../bin/R.exe mkdir -p ../../../bin cp Rfe.exe ../../../bin/Rscript.exe make[1]: `COPYRIGHTS' is up to date. make --no-print-directory -C ../modules -f Makefile.win \ CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' gcc -std=gnu99 -shared -s -o ../../../bin/i386/Rlapack.dll dlamch.o dlapack.o cmplx.o init_win.o Rlapackrc.o -L../../../bin/i386 -lR -lRblas -lgfortran cp lapack.dll ../../../modules/i386/lapack.dll and there is (obviously) read permissions on those files:...

...# and set CAIRO_HOME to the parent of the win32/win64 directories # # If CAIRO_HOME is not set the devices are not built. CAIRO_HOME = # set this to YES to build static HTML help BUILD_HTML = NO # unset this if you are *not* using MiKTeX MIKTEX = TRUE # additional optimization flags EOPTS=-mtune=core2 # define to -fopenmp if the toolchain has OpenMP support OPENMP = -fopenmp # define to -pthread if the toolchain has pthreads support PTHREAD = -pthread ## ====== configuration macros for building installer =========== # location where Inno Setup 5.[34].x was installed. Spaces allowed. ISDIR=E:...

...----------------------------------- * installing *source* package ?analogue? ... ** libs gcc -std=gnu99 -I/home/gavin/R/devel/build/include -DNDEBUG -I/usr/local/include -fpic -g -O2 -pipe -m64 -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -march=core2 -fasynchronous-unwind-tables -c c_distx.c -o c_distx.o gcc -std=gnu99 -I/home/gavin/R/devel/build/include -DNDEBUG -I/usr/local/include -fpic -g -O2 -pipe -m64 -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -march=core2 -fasynchronous-unwind-tables -c...

...ib.h... yes checking for inline... inline checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes configure: creating ./config.status config.status: creating src/Makevars ** libs x86_64-pc-linux-gnu-g++ -I/usr/lib64/R/include -g -O2 -I/usr/local/include -fpic -O2 -march=core2 -fomit-frame-pointer -fno-ident -fweb -pipe -msse3 -c equalize.cpp -o equalize.o x86_64-pc-linux-gnu-gcc -std=gnu99 -I/usr/lib64/R/include -g -O2 -I/usr/local/include -fpic -O2 -march=core2 -fomit-frame-pointer -fno-ident -fweb -pipe -msse3 -c fftw_access_func.c -o fftw_access_func.o x86_64-pc-linu...

...rts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one core????if so, can we specify the use different core. eg: dom0=core2 domU=core3? xen will use just one core? Thanks Lei -- "We learn from failure, not from success!" ________________________...

...rts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one core????if so, can we specify the use different core. eg: dom0=core2 domU=core3? xen will use just one core? Thanks Lei -- "We learn from failure, not from success!" ________________________...

I noticed a problem using R 2.7.1 on Windows XP SP2 with the precompiled Atlas Rblas.dll. Running the code below causes R to crash. I started R using Rgui --vanilla and am using the precompiled Atlas Rblas.dll from cran.fhcrc.org dated 17-Jul-2007 05:04 for Core2 Duo. The code that causes the crash: x <- rnorm(100) y <- rnorm(100) z <- rnorm(100) loess(z ~ x * y) loess(z ~ x) does not cause a crash using the Atlas BLAS and neither does running the above code with the Rblas.dll that came with R 2.7.1. In addition, the code runs fine using the At...