Petko Manolov wrote: > I don't see the point of string-486.c - string-486.h is a replacement > of string.h for i[45]86 machines so let stay in include directory. The point is it may run faster due to better i-cache usage. Remember also that 486 machines don't have much memory, so the gain from reducing kernel size is more significant. (Less paging etc.) You'd still want string-486.h to _call_ the larger routines in string-486.c, using FASTCALL or your choice of alternate registers. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: [patch] string-486.h modified Richard B. Johnson
- Re: [patch] string-486.h modified Petko Manolov
- Re: [patch] string-486.h modified Richard B. Johnson
- Re: [patch] string-486.h modified Petko Manolov
- Re: [patch] string-486.h modified Pavel Machek
- Re: [patch] string-486.h modified Alan Cox
- Re: [patch] string-486.h modified Petko Manolov
- Re: [patch] string-486.h modified Alan Cox
- Re: [patch] string-486.h modified Jamie Lokier
- Re: [patch] string-486.h modified Petko Manolov
- Re: [patch] string-486.h modified Jamie Lokier
- Re: [patch] string-486.h modified Petko Manolov
- Re: [patch] string-486.h modified Jamie Lokier
- Re: [patch] string-486.h modified Richard B. Johnson
- Re: [patch] string-486.h modified Petko Manolov
- Re: [patch] string-486.h modified Petko Manolov