From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linux-Xtensa] Re: sched_clock always 0 and no process time accounting with 3.11-rc1
Date: Wed, 17 Jul 2013 10:14:06 +0300 [thread overview]
Message-ID: <20130717071406.GE6950@tarshish> (raw)
In-Reply-To: <51E64172.9050808@zankel.net>
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 -
next prev parent reply other threads:[~2013-07-17 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMo8BfLO31GgMMA_hENr0xm=qaUz3EVLtaQ8hewiQHdbV+s6sA@mail.gmail.com>
2013-07-17 6:19 ` sched_clock always 0 and no process time accounting with 3.11-rc1 Baruch Siach
2013-07-17 6:39 ` Max Filippov
2013-07-17 6:47 ` [Linux-Xtensa] " Baruch Siach
2013-07-17 7:02 ` Chris Zankel
2013-07-17 7:14 ` Baruch Siach [this message]
2013-07-17 9:03 ` Russell King - ARM Linux
2013-07-17 9:12 ` Baruch Siach
2013-07-17 9:15 ` Russell King - ARM Linux
2013-07-17 15:15 ` [Linux-Xtensa] " Marc Gauthier
2013-07-17 15:24 ` Russell King - ARM Linux
2013-07-17 16:17 ` Marc Gauthier
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=20130717071406.GE6950@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).