search for: fcse

...ent compile-time options, they are > different input files and command line arguments. If you look at the > LLVM llvm-test makefiles, this information is also encoded. From the > 126.gcc makefile, for example, you'll see: > > RUN_OPTIONS := -quiet -funroll-loops -fforce-mem -fcse-follow-jumps > -fcse-skip-blocks -fexpensive-optimizati > ons -fstrength-reduce -fpeephole -fschedule-insns -finline-functions > -fschedule-insns2 -O -o - > > ifeq ($(RUN_TYPE),test) > STDIN_FILENAME = cccp.i > STDOUT_FILENAME = cccp.s > else > STDIN_FILENAME = amptjp.i...

...f/train) are not different compile-time options, they are different input files and command line arguments. If you look at the LLVM llvm-test makefiles, this information is also encoded. From the 126.gcc makefile, for example, you'll see: RUN_OPTIONS := -quiet -funroll-loops -fforce-mem -fcse-follow-jumps -fcse-skip-blocks -fexpensive-optimizati ons -fstrength-reduce -fpeephole -fschedule-insns -finline-functions -fschedule-insns2 -O -o - ifeq ($(RUN_TYPE),test) STDIN_FILENAME = cccp.i STDOUT_FILENAME = cccp.s else STDIN_FILENAME = amptjp.i STDOUT_FILENAME = amptjp.s endif Note that...

Does anyone know the "standard" commandline to compile and run spec95 benchmarks ? I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not sure if they are the *default ref* configurations. <Some of them seem to use smaller problem sizes.> SPEC95 was retired many years ago, so few people around me know how to compile and run them. I am building from

...ons, they are different input files and command >> line arguments. If you look at the LLVM llvm-test makefiles, this >> information is also encoded. From the 126.gcc makefile, for example, >> you'll see: >> >> RUN_OPTIONS := -quiet -funroll-loops -fforce-mem -fcse-follow-jumps >> -fcse-skip-blocks -fexpensive-optimizati >> ons -fstrength-reduce -fpeephole -fschedule-insns -finline-functions >> -fschedule-insns2 -O -o - >> >> ifeq ($(RUN_TYPE),test) >> STDIN_FILENAME = cccp.i >> STDOUT_FILENAME = cccp.s >> el...

Hello all, I have just installed a Wildcard X100P into an Asterisk box. I connected the line socket to the internal telephone system where I work. The card is identified to asterisk etc, however I am unable to recieve or make calls. When attempting to dial I get: Executing Dial("SIP/1106-ec8b", "Zap/1/644746") in new stack Called 1/644746 Zap/1-1 answered SIP/1106-ec8b Hungup

Currently we have RH7.3 with compiler gcc 2.96.x My mission, should I choose to accept it, involves moving our embedded application to CentOS 4.1 with gcc 3.x Problem is that about 1/2 million lines of code that gcc 2.96 accepts gives fatal fits to the gcc 3.x compiler from CentOS 4.1 I don't know how many fatal fits, as some disguise others etc. "Can't find register to

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See