Re: [Gcl-devel] Cygwin change

[Camm Maguire]

Greetings!  

OK, can you please test this build with making maxima and running its
'make test'?  And then could you try this for the macro?

#define NULL_OR_ON_C_STACK(y) (((void *)(y)) < ((void *)DBEGIN))

Your solution is definitely the right one, but I don't know how we can
be sure that the stack is less than 0x400000, whereas I have more
confidence in it being less than DBEGIN, and I can't see how any other
pointer in the program could point to anything else which might lie
below DBEGIN.

I'll go ahead and commit your change, but please let me know if I can
use DBEGIN instead.

Thanks for your contribution!

Dan Stanger <address@hidden> writes:

> There was really only 1 change, that is to change the definition of
> NULL_OR_ON_C_STACK to:
> 
> #define NULL_OR_ON_C_STACK(y) (((void *)(y)) < ((void *)0x400000))
> 
> I think this is ok as 0 gets checked by this case also.  You also have
> to put the file
> unexnt.c back into the normal cvs.
> Dan
> 
> 
> _______________________________________________
> Gcl-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gcl-devel
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah