You are not logged in.
I am trying to understand the scope of recent changes in gcc. If you have gcc installed on your Atom-based Arch box, please post a few things for me:
grep -m 1 -i atom /proc/cpuinfo
gcc -c -Q -march=native --help=target | grep -i 'march=\|mtune='
On my ancient Atom 330:
% grep -m 1 -i atom /proc/cpuinfo
model name : Intel(R) Atom(TM) CPU 330 @ 1.60GHz
% gcc -c -Q -march=native --help=target | grep -i 'march=\|mtune='
-march= bonnell
-mtune= bonnell
Thank you!
Last edited by graysky (2014-06-07 19:58:00)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
$ grep -m 1 -i atom /proc/cpuinfo
model name : Intel(R) Atom(TM) CPU D410 @ 1.66GHz
$ gcc -c -Q -march=native --help=target | grep -i 'march=\|mtune='
-march= bonnell
-mtune= bonnell
Last edited by 2ManyDogs (2014-06-07 20:05:29)
Offline
Thank you 2md. This is interesting because the mainline kernel code is calling the deprecated -march=atom optons... I believe gcc will just ignore and default to generic.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
same here with
$ grep -m 1 -i atom /proc/cpuinfo
model name : Intel(R) Atom(TM) CPU N450 @ 1.66GHz
$ gcc -c -Q -march=native --help=target | grep -i 'march=\|mtune='
-march= bonnell
-mtune= bonnell
Offline
..[root@arch] - [~] - [Sat Jun 07, 06:08]
..[$] <()> grep -m 1 -i atom /proc/cpuinfo
model name : Intel(R) Atom(TM) CPU N450 @ 1.66GHz
..[root@arch] - [~] - [Sat Jun 07, 06:08]
..[$] <()> gcc -c -Q -march=native --help=target | grep -i 'march=\|mtune='
-march= bonnell
-mtune= bonnell
Offline
$ grep -m 1 -i atom /proc/cpuinfo
model name : Intel(R) Atom(TM) CPU D525 @ 1.80GHz
$ gcc -c -Q -march=native --help=target | grep -i 'march=\|mtune='
-march= bonnell
-mtune= bonnell
Last edited by johane (2014-06-08 21:51:03)
Offline