From mboxrd@z Thu Jan 1 00:00:00 1970 From: baruch@tkos.co.il (Baruch Siach) Date: Wed, 17 Jul 2013 10:14:06 +0300 Subject: [Linux-Xtensa] Re: sched_clock always 0 and no process time accounting with 3.11-rc1 In-Reply-To: <51E64172.9050808@zankel.net> References: <20130717061925.GC6950@tarshish> <20130717064709.GD6950@tarshish> <51E64172.9050808@zankel.net> Message-ID: <20130717071406.GE6950@tarshish> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Chris, On Wed, Jul 17, 2013 at 12:02:10AM -0700, Chris Zankel wrote: > On 07/16/2013 11:47 PM, Baruch Siach wrote: > >> According to C99 the behaviour of (1 << 32) is undefined on platforms with > >> 32 bit int, so it could yield any value. > > But so is ARM, isn't it? > > The handling of constants might be target-architecture dependent. > > On a somewhat related issue, are you using a 32-bit host or 64-bit host? > Note that 64-bit cross compilation is known to be broken for Xtensa, I > had a problem running glibc when compiled with cross compiler on a > 64-bit host. Yes, my host is x86_64. I haven't encountered any problem yet. But thanks for the warning, I'll keep that in mind. I think it's worth a mention in the linux-xtensa wiki. It surly worth a fix as well, I guess. Are there any samples of code that are known to be break with 64 bit host? baruch -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -