Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: Lemmings - a tutorial Part V (last) Message-ID: <20392@cbmvax.commodore.com> Date: 5 Apr 91 07:44:17 GMT References: <1991Mar31.003933.1483@mintaka.lcs.mit.edu> <1991Apr1.020748.26863@mintaka.lcs.mit.edu> <1991Apr4.224045.10542@s Organization: Commodore, West Chester, PA Lines: 46 tarnet.uucp> Sender: Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Followup-To: Distribution: Organization: Commodore, West Chester, PA Keywords: In article <1991Apr4.224045.10542@starnet.uucp> sschaem@starnet.uucp (Stephan Schaem) writes: > And when will you have C compiler with AI? Optimization is not only > tricks, but logical solution for you code. > Again, how many compiler break up large loops for registers usage? Any good modern compiler uses procedure-level optimization, particularily register assignment and common-subexpression elimination. I alpha and beta test compilers, and often go on "missed optimization hunts", trying to determine if I could have coded it any tighter myself (within the semantics of the language). More often than I care to admit, I think I've caught the compiler wasting instructions, and find _far_ later in the routine that the value in question is being reused, saving time/space. I can still catch even the latest ones on some things, but it has been getting a lot harder in the last couple of years. Go pick up or borrow from a library a book on compiler optimization (make sure it's fairly recent, say the last 3 years or so). > assign went way once more!) > -ANYBODY have that problem? like do something and the system dont know > system: anymore or whatever was assigned?- that on A3000. > Or know where to get info on the task that are runing in resident mode? > I know Its the third time I ask help, but maybe someone will se it:-) No one can help you unless you give some indication of what version of the OS you're running (results of the version command). There were problems like that a LONG LONG time ago. You could also have a buggy piece of software that hits memory outside it's allocation. I advise running enforcer all the time, and mungwall either all the time, or whenever testing software or hunting down a problem like this. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup Disclaimer: Nothing I say is anything other than my personal opinion. Thus spake the Master Ninjei: "To program a million-line operating system is easy, to change a man's temperament is more difficult." (From "The Zen of Programming") ;-)