Re: [PATCH] common implementation of iterative div/mod

[Jeremy Fitzhardinge]

Andi Kleen wrote:
> Jeremy Fitzhardinge wrote:
>   
> > Andi Kleen wrote:
> >     
> > > You would need to annotate it and have a separate object file for the
> > > different sections. Also it would need to be compiled PIC.
> > >
> > > Inlining is better.
> > >       
> > BTW, I'm seeing the memcpy() in __vdso_gettimeofday() not being inlined.
> >     
>
> Hmm works here. What compiler do you use? Normally gcc should 
> recognize the memcpy is just two constant stores and always inline even with -Os.
>   

It's:
jeremy@cosworth:~/hg/xen/paravirt/linux-x86_64$ gcc -v
Reading specs from /usr/lib/gcc/x86_64-linux/3.4.4/specs
Configured with: ../src/configure -v 
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr 
--libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4 
--enable-shared --with-system-zlib --enable-nls 
--without-included-gettext --program-suffix=-3.4 --enable-__cxa_atexit 
--enable-libstdcxx-allocator=mt --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-java-gc=boehm --enable-java-awt=gtk 
--disable-werror x86_64-linux
Thread model: posix
gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)

I think this is still a supported compiler, isn't it?

   J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/