Path: chuka.playstation.co.uk!news From: Christoph Luerig Newsgroups: scee.yaroze.programming.codewarrior Subject: Re: NYoptimize problems Date: Thu, 23 Jul 1998 10:12:57 +0200 Organization: PlayStation Net Yaroze (SCEE) Lines: 72 Message-ID: <35B6F089.F1AD4DD0@immd9.informatik.uni-erlangen.de> References: <35B648B6.656A@idirect.com> NNTP-Posting-Host: faui90.informatik.uni-erlangen.de Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------FF91C268B651FDEDACA2321A" X-Mailer: Mozilla 4.04C-SGI [en] (X11; I; IRIX 6.3 IP32) --------------FF91C268B651FDEDACA2321A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit John MacPherson wrote: > I decided inside my project to change from NYdebug to NYoptimized and > when I relinked the exact same program I got a bizarre error where > reading the controller in a certain function no longer worked. When I > switched it back to NYdebug the problem went away. Is there anything > special I should know about "NYoptimize"? Hi John! I got some problem of this also, when I used a "long" variable in a variable in a function, that was used for some calculation. According to the behaviour of the program, the variable ws not handled as long in the optimized version any more. When I declared it volatile everything went O.K. If you are requesting the pads however you must declare the variables volatile, that you get from the GetPadBuf function. If you have already declaerd it volatile have a look around if there are other vriables involved and declare them also volatile. Christoph --------------FF91C268B651FDEDACA2321A Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit John MacPherson wrote:
I decided inside my project to change from NYdebug to NYoptimized and
when I relinked the exact same program I got a bizarre error where
reading the controller in a certain function no longer worked.  When I
switched it back to NYdebug the problem went away.  Is there anything
special I should know about "NYoptimize"?






Hi John!






I got some problem of this also, when I used a "long" variable in a variable in a function, that was used for some calculation.



According to the behaviour of the program, the variable ws not handled as long in the optimized version any more.



 When I declared it volatile



everything went O.K. If you are requesting the pads however you must declare



the variables volatile, that you get from the GetPadBuf function. If you have already declaerd it volatile have a look around if there



are other vriables involved and declare them also volatile.






Christoph 

 

--------------FF91C268B651FDEDACA2321A--