| 1 |
Am Mittwoch, 14. Januar 2015, 12:58:21 schrieb Michał Górny: |
| 2 |
> |
| 3 |
> Solution: per-arch USE_EXPANDs for flags, e.g.: |
| 4 |
> |
| 5 |
> CPU_FLAGS_X86="3dnow 3dnowext avx ..." |
| 6 |
> CPU_FLAGS_ARM="neon ..." # arm* flags? |
| 7 |
> CPU_FLAGS_MIPS="..." # mips* flags? |
| 8 |
> |
| 9 |
|
| 10 |
I like it, because it standardizes and removes causes for confusion. So, +1. |
| 11 |
|
| 12 |
That said, long time ago I was taught that "instruction set use-flags" should |
| 13 |
be avoided as much as possible. I don't remember the source for that anymore. |
| 14 |
|
| 15 |
Question to all, is that documented anywhere, and what are the specifics? |
| 16 |
I suspect "use flags that only switch CFLAGS etc" are forbidden, "useflags |
| 17 |
that enable assembler code etc" are allowed? |
| 18 |
|
| 19 |
-- |
| 20 |
|
| 21 |
Andreas K. Huettel |
| 22 |
Gentoo Linux developer |
| 23 |
dilfridge@g.o |
| 24 |
http://www.akhuettel.de/ |
Archives