From: David Edelsohn <dje@watson.ibm.com>
To: Robert Neugebauer <rneugeba@undergrad.math.uwaterloo.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: RS6000 to G4 assembly changes
Date: Sat, 22 Jan 2000 21:15:53 -0500 [thread overview]
Message-ID: <200001230215.VAA21612@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Robert Neugebauer <rneugeba@undergrad.math.uwaterloo.ca> of "Sat, 22 Jan 2000 01:45:00 EST." <Pine.SOL.3.96.1000122013827.17059B-100000@fitch.math.uwaterloo.ca>
>>>>> Robert Neugebauer writes:
Robert> I am not trying to build a cross compiler, I am not trying to build GCC.
Robert> My course at university uses its own compiler called uC++ (Micro C++).
Robert> The compiler thus far only has the following targets that work:
...
Robert> dmake ibm-rs6000
...
Robert> By my knowledge rs6000 is a RISC based architecture, thus I tried to build
Robert> uC++ using the target ibm-rs6000. This resulted in an unrecognized opcode
Robert> movl during compilation.
Robert> If someone knows what the similar instruction on my G4 is, and any other
Robert> problems I might/will encounter, I would appreciate it.
Neither the original POWER architecture (aka "rs6000"), nor the
PowerPC architecture contain a "movl" instruction and/or mnemonic. You
said above that target ibm-rs6000 works, but I assume that you mean it is
a uC++ target you are attempting to use. If uC++ is producing that
instruction for the "rs6000" architecture, then there is something
severely wrong with its ibm-rs6000 target that has nothing to do with
POWER versus PowerPC ("G4") architectures.
If the ibm-rs6000 uC++ target is suppose to work, then it still
might be a problem of lingering x86 configuration files that were not
cleared when you tried to build the ibm-rs6000 target.
Gabriel Paubert gave a good summary of the differences between the
related architectures and what would need to be changed in the ibm-rs6000
target of the uC++ compiler to generate correct PowerPC code.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-23 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 18:40 RS6000 to G4 assembly changes Robert Neugebauer
2000-01-21 19:08 ` David Edelsohn
2000-01-21 22:53 ` Robert Neugebauer
2000-01-22 0:16 ` David Edelsohn
2000-01-22 6:45 ` Robert Neugebauer
2000-01-22 12:21 ` Gabriel Paubert
2000-01-22 16:01 ` Robert Neugebauer
2000-01-22 23:45 ` Bill Studenmund
2000-01-23 2:15 ` David Edelsohn [this message]
2000-01-22 11:16 ` Giuliano Pochini
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=200001230215.VAA21612@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rneugeba@undergrad.math.uwaterloo.ca \
/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).