buildroot/arch
Peter Korsgaard 80e4060908 arch/Config.in.x86: drop BR2_x86_generic
The fuzzy generic x86 variant doesn't make much sense in the context of
Buildroot, and the recent change to use -march instead of -mtune broke it.

From the GCC manual:

https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/i386-and-x86-64-Options.html#i386-and-x86-64-Options:

-mtune=cpu-type
    Tune to cpu-type everything applicable about the generated code,
    except for the ABI and the set of available instructions. While
    picking a specific cpu-type schedules things appropriately for that
    particular chip, the compiler does not generate any code that cannot
    run on the default machine type unless you use a -march=cpu-type
    option. For example, if GCC is configured for i686-pc-linux-gnu then
    -mtune=pentium4 generates code that is tuned for Pentium 4 but still
    runs on i686 machines.

    The choices for cpu-type are the same as for -march. In addition,
    -mtune supports 2 extra choices for cpu-type:

    ‘generic’
        Produce code optimized for the most common IA32/AMD64/EM64T
        processors. If you know the CPU on which your code will run,
        then you should use the corresponding -mtune or -march option
        instead of -mtune=generic. But, if you do not know exactly what
        CPU users of your application will have, then you should use
        this option.

        As new processors are deployed in the marketplace, the behavior
        of this option will change. Therefore, if you upgrade to a newer
        version of GCC, code generation controlled by this option will
        change to reflect the processors that are most common at the
        time that version of GCC is released.

        There is no -march=generic option because -march indicates the
        instruction set the compiler can use, and there is no generic
        instruction set applicable to all processors. In contrast,
        -mtune indicates the processor (or, in this case, collection of
        processors) for which the code is optimized.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-11-07 19:51:06 +01:00
..
Config.in arch: remove the BR2_GCC_TARGET_TUNE option 2014-11-07 00:16:47 +01:00
Config.in.aarch64 arch/arm: always has atomic ops 2014-08-18 11:00:51 +02:00
Config.in.arc arc: add support of ARC HS38 core 2014-11-02 22:25:27 +01:00
Config.in.arm arch/arm: remove BR2_GCC_TARGET_ARCH definitions on ARM 2014-11-07 00:07:34 +01:00
Config.in.avr32 arch/avr32: always has atomic ops 2014-08-18 11:01:22 +02:00
Config.in.bfin arch/bfin: always has atomic ops 2014-08-18 11:01:31 +02:00
Config.in.m68k arch/m68k: get rid of BR2_GCC_TARGET_TUNE 2014-11-07 00:14:13 +01:00
Config.in.microblaze arch/microblaze: always has atomic ops 2014-08-18 11:02:31 +02:00
Config.in.mips arch/mips: always has atomic ops 2014-08-18 11:02:41 +02:00
Config.in.nios2 arch/nios2: always has atomic ops 2014-08-18 11:02:51 +02:00
Config.in.powerpc arch/powerpc: get rid of BR2_GCC_TARGET_TUNE 2014-11-07 00:13:49 +01:00
Config.in.sh arch/sh: always has atomic ops 2014-08-18 11:03:02 +02:00
Config.in.sparc arch/sparc: get rid of BR2_GCC_TARGET_TUNE 2014-11-07 00:13:08 +01:00
Config.in.x86 arch/Config.in.x86: drop BR2_x86_generic 2014-11-07 19:51:06 +01:00
Config.in.xtensa arch/xtensa: always has atomic ops 2014-08-18 11:03:28 +02:00