From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Robert Hancock <hancockr@shaw.ca>,
Christian Kujau <lists@nerdbynature.de>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH] common implementation of iterative div/mod
Date: Wed, 14 May 2008 13:58:57 +0100 [thread overview]
Message-ID: <482AE211.9040907@goop.org> (raw)
In-Reply-To: <482ACB24.5080400@firstfloor.org>
Andi Kleen wrote:
>> 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?
>>
>
> Yes. Here's a patch. You probably didn't see problems because you either
> don't have a glibc that supports the vdso or none of your programs
> gets the timezone from gettimeofday() [that is very obscure obsolete
> functionality anyways, normally it should be gotten from the disk locales]
>
Patch looks fine to me. I just noticed the call to memcpy by
inspection; I haven't tried to run this.
J
prev parent reply other threads:[~2008-05-14 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.QTbvQYXhEm5VNP5dvkl5JG7NHYQ@ifi.uio.no>
2008-05-04 17:35 ` undefined reference to __udivdi3 (gcc-4.3) Robert Hancock
2008-05-04 22:19 ` Segher Boessenkool
2008-05-07 9:29 ` Jeremy Fitzhardinge
2008-05-08 15:16 ` [PATCH] common implementation of iterative div/mod Jeremy Fitzhardinge
2008-05-08 20:26 ` Andrew Morton
2008-05-08 22:00 ` Jeremy Fitzhardinge
2008-05-08 20:52 ` Segher Boessenkool
2008-05-08 21:57 ` Jeremy Fitzhardinge
2008-05-09 11:45 ` Christian Kujau
2008-05-14 6:46 ` Andrew Morton
2008-05-14 7:33 ` Jeremy Fitzhardinge
2008-05-14 8:33 ` Andi Kleen
2008-05-14 9:55 ` Jeremy Fitzhardinge
2008-05-14 10:50 ` Andi Kleen
2008-05-14 10:52 ` Jeremy Fitzhardinge
2008-05-14 11:21 ` Andi Kleen
2008-05-14 12:58 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=482AE211.9040907@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hancockr@shaw.ca \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mingo@elte.hu \
--cc=segher@kernel.crashing.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox