-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

M. Edward (Ed) Borasky wrote:
> Anton Ertl wrote:
>> "M. Edward (Ed) Borasky" wrote:
>>> OK ... I'm back to testing this on my systems. As I noted before, on the
>>> 32-bit system (Athlon TBird) it compiles fine without the
>>> "-enable-force-reg" but crashes with it. Details:
>>>
>>> ./engine.c:463: error: unable to find a register to spill in class 
>>> â??CREGâ??
>> This sounds like it does not compile fine.
> 
>> Actually, this is a typical error I see when using --enable-force-reg,
>> if the explicit register allocations are too restrictive for the
>> compiler.  If you get this with --enable-force-reg, I don't consider
>> this a gcc bug.
> 
>>> $ gcc --version
>>> gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.1)
>> Ok, I have tested on Debian (32-bit) with:
> 
>> gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
> 
>> It compiles fine, and gforth, gforth-itc, and gforth-ditc run fine,
>> but I found and fixed a bug that made gforth-fast hang (now
>> gforth-fast runs fine there, too).  I don't know if this fixes your
>> problem.

I just downloaded the latest source from CVS and did two things:

1. Installed "ffcall" -- that wasn't on my machine and may be on yours.
2. Did a "BUILD-FROM-SCRATCH" using gforth 0.6.9 *without*
- --enable-force-reg as the working gforth

The resulting system does compile with --enable-force-reg and passes all
the "make check" tests. So your change may have fixed my problem, or
"BUILD-FROM-SCRATCH" may have fixed it. I can back the changes out one
at a time and see what the real answer is, but for now, the CVS version
is working. Next step is to try all this with GCC 4.2.0.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG5CoR8fKMegVjSM8RAs68AJ4utxditXN7JfINgn7xpZi0AHlbIgCdFPpP
mC/P0oM8APPY5/76bqxRKQM=
=KrMA
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to