From: Grant Erickson <grant@lcse.umn.edu>
To: linuxppc-embedded@lists.linuxppc.org
Cc: Daniel Nilsson <daniel.n.nilsson@home.se>,
Adrian Cox <apc@agelectronics.co.uk>, Wolfgang Denk <wd@denx.de>
Subject: Bug Discovered in Binutils/GCC for PPC403
Date: Thu, 28 Oct 1999 12:31:02 -0500 [thread overview]
Message-ID: <Pine.SGI.4.10.9910281224020.695157-100000@sapphire.lcse.umn.edu> (raw)
In-Reply-To: <Pine.SGI.4.10.9910281200550.695157-100000@sapphire.lcse.umn.edu>
For those of you working with the TiVo Linux sources, I discovered bug in
binutils-2.9.1.0.25 and binutils-2.9.5.0.14 that results in the following
sorts of error:
foobar.c: Assembler messages:
foobar.c:7868: Error: junk at end of line: `28'
It appears that the assembler has the incorrect definition for the
'dcread' instruction:
In the file binutils-2.9.5.0.14/opcodes/ppc-opc.c, the definition is as
follows:
{ "dcread", X(31,486), XRT_MASK, PPC403, { RA, RB } },
However, according to the IBM PowerPC 403GCX manual the definition is:
dcread RT,RA,RB
The patch to fix this is:
{ "dcread", X(31,486), X_MASK, PPC403, { RT, RA, RB } },
Patch the ppc-opc.c file and rebuild binutils and you're back on your way.
Otherwise, just comment out the offending line of code, such as:
asm("dcread %0,0,%1" : "=r" (tag) : "r" (p));
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~1999-10-28 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SGI.4.10.9910281200550.695157-100000@sapphire.lcse.umn.edu>
1999-10-28 17:31 ` Grant Erickson [this message]
1999-10-28 18:13 ` TiVo Kernel for 403GCX Update (was Re: Support for IBM CPUs?) Jason Haas
1999-11-01 19:20 ` ASM-PPC Include File Rework Proposal: Processor / Board Header Files Grant Erickson
1999-11-02 19:22 ` Dan Malek
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=Pine.SGI.4.10.9910281224020.695157-100000@sapphire.lcse.umn.edu \
--to=grant@lcse.umn.edu \
--cc=apc@agelectronics.co.uk \
--cc=daniel.n.nilsson@home.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.