| delorie.com/archives/browse.cgi | search |
| From: | JeLlyFish DOT software AT gmx DOT net (Vinzent Hoefler) |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: Allegro + gcc295? |
| Date: | Fri, 20 Aug 1999 07:56:11 GMT |
| Organization: | JeLlyFish software |
| Lines: | 15 |
| Message-ID: | <7plm4n$22d$1@news03.btx.dtag.de> |
| References: | <37BDB6A6 DOT 33B9AC90 AT sprint DOT ca> |
| Mime-Version: | 1.0 |
| X-Trace: | news03.btx.dtag.de 935222231 2125 777000109768-0001 990821 07:57:11 |
| X-Complaints-To: | abuse AT t-online DOT de |
| X-Sender: | 777000109768-0001 AT t-online DOT de |
| X-Newsreader: | Forte Free Agent 1.11/16.235 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
Orlando Vazquez <ovazquez AT sprint DOT ca> wrote: >Maybe its just my circumstances, but allegro used to compile alright >with gcc281, but upon recompiling with 295 i get: I got the same problem. The solution is easy, simply comment out (or delete) all the mentioned "%eax". GCC 2.95 seems to have another idea about register spilling. Seems that the register holding the return value is not "spilled" anymore... Vinzent.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |