gcc arch

Config.cache configuration file # vim Config.cache Libc_cv_forced_ Unwind=yes Libc_cv_c_cleanup=yes Libc_cv_arm_tls=yes #.. /configure--host= $TARGET--target= $TARGET--prefix= $TARGET _prefix--enable-add-ons--disable-profile--cache-file= Config.cache--with-binutils= $PREFIX/bin--with-headers= $TARGET _prefix/include cc= $TARGET-gcc cflags= "-G o2– March-armv6 " Note: The CC and cflags to modify will affect the subsequent compilation of

to set up Yum source.After installing CentOS, it is generally necessary to modify the Yum source to achieve the desired speed when installing the update RPM package. Domestic relatively fast has 163 source, Sohu source. Here is an example of a 163 source.1. CD/ETC/YUM.REPOS.D2. MV Centos-base.repo Centos-base.repo.backup3. wget Http://mirrors.163.com/.help/CentOS6-Base-163.repo4. MV Centos6-base-163.repo Centos-base.repo5.yum Clean AllThis article is from the Linux learning blog, so be sure to

directory sequentially: gmp-6.0.0 mpc-1.0.2 mpfr-3.1.2 ppl-1.1 cloog-0.18.1 Perform: ./configure--prefix=/home/charles/code/build_toolchain/toolchain make make install 4. Create Bootstrap GCC Create directory Build/gcc_first and enter into this directory to execute: .. /.. /src/gcc-4.8.2/configure--build=i686-pc-linux-gnu --target=arm-linux-gnueabi--prefix=/home/charles/code/ Build_toolchain/toolchain

,objc,obj-c++--prefix=/usr--program-suffix=-4.6--enable-shared-- Enable-linker-build-id--with-system-zlib--libexecdir=/usr/lib--without-included-gettext--enable-threads=posix- -with-gxx-include-dir=/usr/include/c++/4.6--libdir=/usr/lib--enable-nls--with-sysroot=/--enable-clocale=gnu-- Enable-libstdcxx-debug--enable-libstdcxx-time=yes--enable-gnu-unique-object--enable-plugin--ENABLE-OBJC-GC-- Enable-targets=all--disable-werror--with-arch-32=i686--with-

Scope extension GCC support scope, in many aspects of C language can be used. One of these is the case statement in the Switch/case block. In a complex conditional structure, it is common to rely on nested IF statements to achieve the same results as listing 2 (see./linux/drivers/scsi/sd.c), but listing 2 is simpler. You can also use Switch/case to perform compiler optimizations by using a jump table implementation.Listing 2. Using Scope

ages = C, C ++, Fortran, objc, OBJ-C ++ -- prefix =/usr -- enable-shared -- enable-multiarch -- enable-linker-Build-id -- With-system-zlib -- libexecdir =/usr/lib -- without-included-gettext -- enable-threads = POSIX -- With-gxx-include-Dir =/usr/include/C ++/4.4 -- Program-suffix =-4.4 -- enable- NLS -- enable-clocale = GNU -- enable-libstdcxx-Debug -- enable-plugin -- enable-objc-GC -- enable-targets = all -- disable-werror -- With-arch-32 = iworkf

=-4.4 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnuThrea

-- enable -plugin -- enable-objc-gc -- disable-werror -- with-arch-32 = i686 -- with-tune = generic -- enable-checking = release -- build = x86_64-linux-gnu -- host = x86_64-linux-gnu -- target = x86_64-linux-gnuThread model: posixGcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)COLLECT_GCC_OPTIONS = '-static ''-v''-fno-builtin''-mtune = generic ''-march = x86-64'/Usr/lib/gcc/x86_64-linux-gnu/4.6/PC3-quiet-

operation is legal, for example, if there is such a command ASM ("Movl % 0, % 1"::"M"(FOO ),"M"(Bar); if you use the GCC-C-s option to compile the source file, then in the generated Assembly file, you will see that a command such as movl Foo and bar is generated, this is obviously incorrect. this error will be found later in the compilation check.Variable output: according to the specified output delimiter, the register content is output to a memory

):), compiled as: #APP MOVL Foo,eax #NO_APP MOVL Eax,bar The statement is a bit weird, but it's a good representation of how GCC works. Take a piece of code in ARCH/I386/KERNEL/APM.C as an example, let's compare what happens before and after they compile: Compiled Code of source program __ASM__ ( "Pushl%%edi/n/t" "Pushl%%ebp/n/t" "Lcall%%cs:/n/t" "SetC%%al/n/t" "Addl%1,%2/n/t" "Popl%%ebp/n/t" "Pop

transaction check ---> Package glibc-headers.x86_64 0: 2. 17-222.el7 will be installed --> Processing dependency: Kernel-headers> = 2.2.1 For package: glibc-headers-2.17-222.el7.x86_64 --> Processing dependency: Kernel-headers for package: glibc-headers-2.17-222.el7.x86_64 --> Running transaction check ---> Package kernel-headers.x86_64. 10.0-862.14.4.el7 will be installed --> Finished dependency resolution Dependencies resolved ========================================================== =======

static connections. Below we attach the source code hello. C: #include Run the GCC-static -- verbose-fno-builtin hello. C, -- verbose command to enter the compilation details.-fno-builtin prevents the compiler from converting printf to puts. The result is as follows: Using built-in specs.Collect_gcc = gccCollect_lto_wrapper =/usr/lib/GCC/x86_64-linux-gnu/4.6/Lto-wrapperTarget: x86_64-linux-gnuConfigure

How to compile a cross-platform gcc, the so-called cross-platform means that GCC compiles in a machine type but the compiled application is on a machine type, which we refer to as a cross-platform compilation of this article is reproduced in: http://preshing.com/ 20141119/how-to-build-a-gcc-cross-compiler/ How to build a