Wouter Verhelst <[EMAIL PROTECTED]> writes:
> On Thu, Nov 09, 2006 at 02:14:51PM +0100, Richard Zidlicky wrote:
>> On Thu, Nov 09, 2006 at 12:11:13AM +0100, Wouter Verhelst wrote:
>> > Well, it works until I reach second/MMU030_asm.S; the same error occurs
>> > there, and I obviously can't comment it out (since then the pmove
>> > instructions that are used there will break).
>> >
>> > I've found that by replacing .chip with .cpu, it compiles. However, I'm
>> > not sure whether this is actually the right thing to do
>>
>> does
>> .chip 68030
>> work?
>
> Well, that's what it said in that particular file. That didn't work.
>
> With .cpu 68030, it compiles; however, I'm not sure they actually do the
> same thing, and that's what I'm concerned about.
>
> Oh well, it's not as if I'll be uploading this package without prior
> testing -- I'll find out soon enough ;-)
Isn't the only effect of this instruction to specify what instructions
are allowed so you get warnings if you use something not available on
the chip?
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
