| 1 |
Walter Dnes wrote: |
| 2 |
> gcc -march=native -Q --help=target |
| 3 |
|
| 4 |
If that shows something disabled that cat /proc/cpuinfo shows as |
| 5 |
available, is it safe to turn it on? So far all I have found that is |
| 6 |
disabled that cpuinfo shows is mmx. I'm still looking tho. |
| 7 |
|
| 8 |
Also, I think the native setting is a setting that is known to be 100% |
| 9 |
safe. It is likely one of those things that if you use anything not |
| 10 |
safe and have problems, you get to keep the pieces. I think if the CPU |
| 11 |
supports it should be fine to turn but wanted to ask and make sure. I |
| 12 |
paid almost $200 for my CPU and I would like to get $200 out of it and |
| 13 |
use it all. I bought the whole thing so may as well use the whole |
| 14 |
thing. ;-) |
| 15 |
|
| 16 |
Thoughts? |
| 17 |
|
| 18 |
Dale |
| 19 |
|
| 20 |
:-) :-) |
| 21 |
|
| 22 |
-- |
| 23 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
| 24 |
|
| 25 |
Miss the compile output? Hint: |
| 26 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives