Re: X86-64 uses generic string functions (strlen, strchr, memcmp, ...)

* Jann Horn wrote: > Hi! > > I noticed that X86-64 is using the generic string functions from > lib/string.c for things like strlen(), strchr(), memcmp() and so on. > Is that an intentional omission, because they're not considered worth > optimizing, or is this an oversight? The kernel

Re: X86-64 uses generic string functions (strlen, strchr, memcmp, ...)

* Jann Horn wrote: > Hi! > > I noticed that X86-64 is using the generic string functions from > lib/string.c for things like strlen(), strchr(), memcmp() and so on. > Is that an intentional omission, because they're not considered worth > optimizing, or is this an oversight? The kernel

X86-64 uses generic string functions (strlen, strchr, memcmp, ...)

Hi! I noticed that X86-64 is using the generic string functions from lib/string.c for things like strlen(), strchr(), memcmp() and so on. Is that an intentional omission, because they're not considered worth optimizing, or is this an oversight? The kernel doesn't use string functions much, but if

X86-64 uses generic string functions (strlen, strchr, memcmp, ...)

Hi! I noticed that X86-64 is using the generic string functions from lib/string.c for things like strlen(), strchr(), memcmp() and so on. Is that an intentional omission, because they're not considered worth optimizing, or is this an oversight? The kernel doesn't use string functions much, but if