Hi Joseph,

> Hello, Manuel,
> I just noted an error in the compilation of bind-exit for the jvm backend. 
> The error can be seen in the recette for the Pthread library. With some 
> digging, I was able to undercover that the problem is introduced when the 
> return-goto optimization is enabled. When disabled, the recette runs 
> successfully. Digging a little further, I narrowed the problem to the 
> mark-set-exit! procedure in comptime/Integrate/a.scm. If I comment out the 
> second  forceG? assignment, the pthread recette also runs successfully, even 
> with the return-goto optimizatino in place. Given your comment earlier in the 
> procedure and the fact I am not completely sure I understand what is going on 
> here, I have not submitted this change as a fix. Is this a reasonable 
> modification to fix the problem we are seeing in the pthread recette? 
You are absolutely correct. There is an inconsistency in the compilation
configuration. The JVM backend lacks one construct that is required in
order to avoid generating true escape sequences and the current compilation
does not reflect that. I have fixed it now and I'm preparing a new tarball.

> Also, I just submitted a pull request for changes to the Bigloo C runtime to 
> accommodate C23 and GCC 15 compatibility. See 
> https://github.com/manuel-serrano/bigloo/pull/133. When you have time, please 
> take a look. 
I have seen that. This was a significant effort of yours, so many files needed
some fixes. Thanks a lot!

-- 
Manuel

Attachment: signature.asc
Description: PGP signature

Reply via email to