| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] more improvement to dev_alloc_name -- strnchr |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Mon, 19 Jan 2004 22:15:15 +0100 |
| Cc: | davem@xxxxxxxxxx, ap@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040119130744.324f582b.shemminger@xxxxxxxx> |
| References: | <1074302619.40088e9bd44a6@xxxxxxxxxxxxxxx> <20040119113204.5913a8d6.shemminger@xxxxxxxx> <20040119210605.3cea32b0.ak@xxxxxxx> <20040119130744.324f582b.shemminger@xxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 19 Jan 2004 13:07:44 -0800 Stephen Hemminger <shemminger@xxxxxxxx> wrote: > On Mon, 19 Jan 2004 21:06:05 +0100 > Andi Kleen <ak@xxxxxxx> wrote: > > > On Mon, 19 Jan 2004 11:32:04 -0800 > > Stephen Hemminger <shemminger@xxxxxxxx> wrote: > > > > > +#ifndef __HAVE_ARCH_STRNCHR > > > > Please drop the ifdef. Don't want to encourage anybody to write > > strrchr() in assembly. > > > > -Andi > > I assume you mean strnchr not strrchr. Mainly just following the style > of all the other string routines. Yep, strnchr. > What if gcc does it inline in some future version? Not sure what it has to do with that. The #ifdef __HAVE_ARCH_* stuff is that architectures with crazy enough hackers can add assembly optimized functions if they want. But it clearly doesn't make any sense with this function (in fact it doesn't make much sense with any string function except memset/memcpy), so better not encourage it. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Hot-plug for pcnet32 ?, Donald Becker |
|---|---|
| Next by Date: | Re: [PATCH] more improvement to dev_alloc_name -- strnchr, David S. Miller |
| Previous by Thread: | Re: [PATCH] more improvement to dev_alloc_name -- strnchr, Stephen Hemminger |
| Next by Thread: | Re: [PATCH] more improvement to dev_alloc_name -- strnchr, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |