Path: chuka.playstation.co.uk!scea!pro1-150.barrie.connex.net!user From: developer@woodentulip.com (Sean Kennedy) Newsgroups: scee.yaroze.programming.codewarrior,scea.yaroze.programming.codewarrior Subject: Re: GTE asm with CodeWarrior Date: Tue, 26 Jan 1999 00:13:08 -0500 Organization: Wooden Tulip Ltd. Lines: 87 Message-ID: References: <78dk65$nd41@chuka.playstation.co.uk> <36AAF8E8.E85886FB@hinge.mistral.co.uk> <78f5ll$nd46@chuka.playstation.co.uk> <36AB8574.82169D5F@hinge.mistral.co.uk> NNTP-Posting-Host: pro1-150.barrie.connex.net Xref: chuka.playstation.co.uk scee.yaroze.programming.codewarrior:438 scea.yaroze.programming.codewarrior:381 > John Blackburne wrote: > > > This is certainly not the place to discuss GTE internals. If you had a license > > > for that information you would have got the GTE inline definitions header > > > file from Metrowerks - but as you are only using the Yaroze version of CW, > > > you won't have it (and won't get it - it comes with the ProDev version which > > > costs several thousand pounds more and is only available to developers). Very true, about the Commercial version, but to save time and money Metrowerks used the same code base for th Yaroze IDE as they did with the Commercial IDE. With Bits Yanked out. That does not mean that the Yaroze system can be used for Assembler programming. When the North American Groove crew were in the SCEA management of the Yaroze program, there was an open invitation for those who whished to investigate R3000 assembler to request the information from the contact staff. Sadly those individuals left. And now no one knows what we are talking about. There was some sample FMV sequence players that could work on Yaroze too. Trouble was, the library had those elements removed, and the lib was from Metrowerks. It was encapsulated in the Software-Floating point library. > > It's unfortunate this is not clearer with the Yaroze kit and with > > Codewarrior for Net Yaroze. First the assembler documentation is minimal, > > with no list of supported op-codes and symbols, and I couldn't find any asm > > sample code to indicate what's possible. Then when I tried compiling some > > GTE code some of the GTE op-codes did compile, e.g. CW has no problems with > > mtc2 and ctc2. So it looked like either I was using the wrong syntax or CW's > > GTE asm implementation was incomplete. Hah, nothing in the "documentation" says anything there but I noticed a few Metrowerks examples and .h files that contained defintions that allowed GTE / GPU optimizations in assembler. > Shhh. > If I were you I'd stop discussing GTE op-codes in these groups. If you were a > developer, > you'd have the manuals (some of them anyway) and the support. If not, you've picked > up some stuff from a hacker site and are in danger of getting a revoked yaroze > membership (I've never heard of it happening, but the threat is there if you aren't > careful). Wait a minute here. The assembler will ony make sense to those that know what its true register designation defintions do and are documented. There is no supporting documentation, and the code is relatively unintellagable. I code in assembler, and what I see there looks like someone tried using a code snippet without knowing what goes on. > > But it looks like I'd need the pro version to do this sort of programming. I > > suspected this might be the case but my partial success with CW for NY had > > got my hopes up. Oh well, Nice motives, just stick to what you know you can do with supporting documentation. As well use what the compiler can support in assembly language, and not someone elses "Tweaks" that are part of a different developer product. > It's the license, not the compiler that is difficult to get. Metrowerks are VERY > helpful if you've got a license.... > Craig. Yes and no. It all comes down to what you wan to do, and what knowledge you have to do it. Assembler is a very powerful developer tool if you know EXACTLY what you are doing at ALL Times. This example is a clear case of someone who got a code snippet, and tried using it without proper file/library support in the compiler. However, if Sony had released an assembler fragment to allow "lets say" Force feedback control as part of the GetPadBuf() routine, to allow an output. Called PutPadBuf( *padFF_Info ) and there was good documentation support. Then Yes Metrowerks CW for Net Yaroze can compile the assembler source, and it would work. But it is easier to maintain these hooks in Library Upkeep in the file: LIBPS.A Assembler is like digging a post hole with a teaspoon. Keep in mind, you have control over EVERY Little Piece of Dirt. -sean