On 05/13/2015 07:42 AM, Geert Uytterhoeven wrote:
On Wed, May 13, 2015 at 4:09 PM, Michele Curti [off-list ref] wrote:
quoted
Tried to transpose rows with columns, to avoid architecture name duplication
and to get only one table while keeping 80 char width, but result seems less
readable :p
m
i u
b c o n
l h r m p p i
a e o n e p o c x
a a a c x m b 1 n n a w s s o t
l r v k c a i m m e l m 0 i r r e s c p t r e
p a a m r f c r f g a 3 6 t a i 3 o i i r 3 o a i e x n
h r r 6 3 i 6 i r o 6 2 8 a z p 0 s s s p 9 r s r l u 3 8 s
a c m 4 2 n x s v n 4 r k g e s 0 2 c c c 0 e h c e m 2 6 a
-------------------------------------------------------------------------------
lockdep T K K K K K T T T K T T T K K K T T T T K K K K K K K K K K
stackprotector T T K K T T T T T T T T T T T K T T T T T T T K T T T T K T
jump-labels T T K K T T T T T T T T T T T K T T T T K K T T K T T T K T
seccomp-filter T T K K T T T T T T T T T T T K T T T T T K T T T T T T K T
I thought about that, too, as there are more (not fully implemented) features
than architectures. But I expect more merge conflicts with the transposed
version.
There is another reason for the transposed version, which is that it
makes adding features to the list much easier. At the same time, plain
ASCII is horrific for maintaining tables...
-hpa