Bug#448370:

This bug still exists in GCC 4.6. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktiklns8uptebakpudjg-kj30xdb...@mail.gmail.com

Bug#448370: Acknowledgement (gcc-4.2: gcc screws up "-mtune" when "-march=native" is used)

BTW, I just tried the same test-case on a different machine -- and it seems to work properly there (-march=native results in a correct default value for -mtune). The only real difference between the machines is that the previous machine (where gcc showed the bug) has a pentium3 cpu, whereas the cu

Bug#448370: gcc-4.2: gcc screws up "-mtune" when "-march=native" is used

Package: gcc-4.2 Version: 4.2.2-3 Severity: normal The option "-march=native" can be used to set the target architecture from the current host (and "-mtune=native" should do the same thing for tuning). By my reading of the docs, "-march=native" should otherwise work just like any other -march o