From: David Brownell <david-b@pacbell.net>
To: linux-omap@vger.kernel.org
Subject: rdhi, rdlo and rm must all be different: say what??
Date: Wed, 12 Mar 2008 16:58:40 -0800 [thread overview]
Message-ID: <200803121758.41024.david-b@pacbell.net> (raw)
I did a build for H4, using the CodeSourcery 2007q3-53 toolchain, and:
CC kernel/sched.o
/tmp/ccePvKYj.s: Assembler messages:
/tmp/ccePvKYj.s:16: rdhi, rdlo and rm must all be different
/tmp/ccePvKYj.s:1243: rdhi, rdlo and rm must all be different
The problem doesn't crop up with a build for OSK; different CPUs,
presumably. It turns out these are both umull instructions; if
I "make kernel/sched.s" and build the result, the relevant lines
have different numbers but match up as:
sched_clock:
16: umull r0, r1, r0, r3 @ tmp136, jiffies.371, tmp137
sched_slice:
...
1243: umull r0, r1, r0, r2 @ slice.2262, slice, <variable>.load.weight
So this all looks suspiciously buglike. Does anyone know how
to fix this issue? Is it really a problem?
- Dave
next reply other threads:[~2008-03-13 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 0:58 David Brownell [this message]
2008-03-13 7:35 ` rdhi, rdlo and rm must all be different: say what?? Felipe Balbi
2008-03-13 10:20 ` David Brownell
2008-03-13 15:54 ` Woodruff, Richard
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=200803121758.41024.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.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