Re: [PATCH] provide out-of-line strcat() for m68k

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Roman Zippel <zippel@...>
Cc: Al Viro <viro@...>, <torvalds@...>, <geert@...>, <linux-m68k@...>, <linux-kernel@...>
Date: Wednesday, May 21, 2008 - 7:09 am

On Wed, May 21, 2008 at 12:53:34PM +0200, Roman Zippel wrote:

Then it's worth mentioning in Documentation/Changes, IMO...  Anyway,
updating m68k toolchain is not a problem; I'll get around to it tonight.
I still think that out-of-line implementation is a good idea, if nothing
else it would prevent future crap of the same kind if some later version
decides that strlen(a) + strlen(b) can be proven to be less than size
argument of strncat(), etc.

Technically we _are_ in nasal daemon country with redefining str*, unless
we pass -ffreestanding; m68k doesn't, so we can't guarantee that new stuff
of that kind won't crop up.  IOW, it might be a good policy to have fallback
implementations of potentially affected primitives...
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] provide out-of-line strcat() for m68k, Al Viro, (Tue May 20, 9:12 pm)
-ffreestanding or not -ffreestanding, Adrian Bunk, (Wed May 21, 3:52 am)
Re: -ffreestanding or not -ffreestanding, Roman Zippel, (Wed May 21, 7:44 am)
Re: [PATCH] provide out-of-line strcat() for m68k, Roman Zippel, (Tue May 20, 11:34 pm)
Re: [PATCH] provide out-of-line strcat() for m68k, Roman Zippel, (Wed May 21, 6:53 am)
Re: [PATCH] provide out-of-line strcat() for m68k, Al Viro, (Wed May 21, 7:09 am)