Keith Owens <kaos@ocs.com.au> writes: |> On Fri, 12 Apr 2002 17:05:37 +0200, |> Andreas Schwab <schwab@suse.de> wrote: |> >GCC 3 may generate calls to memset, so we need to export it to modules. |> |> If gcc does that the code does not use the arch tuned memset. Also the |> memset function is only generated if __HAVE_ARCH_MEMSET is undefined, |> but include/asm-ia64/string.h defines __HAVE_ARCH_MEMSET. We would be |> better off teaching gcc not to generate calls to memset where we do not |> want them so the kernel gets the code that we want, not what gcc thinks |> might be a good idea. There is no way for gcc to see the memset macro when it generates the call to the memset function. And there isn't much lost anyway, since the macro is just there to call __bzero vs. __memset_generic (aka memset), the difference is just one parameter more or less. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."Received on Fri Apr 12 18:38:48 2002
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:08 EST