Messages in this thread | | | Date | Tue, 18 Feb 2003 23:49:46 +0100 | From | Tomas Szepe <> | Subject | Re: [PATCH] morse code panics for 2.5.62 |
| |
> [jbglaw@lug-owl.de] > > Then, you can have > const char morses[] = { > MORSE2('A', '.', '-'), > MORSE4('B', '-', '.', '.', '.'), > MORSE4('C', '-', '.', '-', '.'), > MORSE3('D', '-', '.', '.'), > MORSE1('E', '.'), > MORSE4('F', '.', '.', '-', '.') > ... > }; > > That's going to take exactly the same memory in the compiled vmlinux > image, *and* it's really readable:-) Of course, gcc will optimize any > added "bloat" away...
Looks good to me, can you send an updated patch?
-- Tomas Szepe <szepe@pinerecords.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |