macOS issues

30 views
Skip to first unread message

Leszek Buczkowski

unread,
May 7, 2025, 6:53:45 PMMay 7
to Picat
I noticed two issues with Picat on macOS (macbook air M3, Sequoia 15.4.1):

- Compilation hangs on toam.c (at least 10 minutes, I did not wait longer). A workaround is to compile toam.c with -O rather than -O3:

CFLAGS1 = -O -DDARWIN -Wall -DGC -fomit-frame-pointer -Wno-error=unused-label # -arch x86_64  MacOS X, Darwin

toam.o  : toam.c term.h inst.h basicd.h basic.h toam.h event.h frame.h emu_inst.h
$(CCC) $(CFLAGS1) toam.c...

- Enter does not work as expected in debugger (picat -d ...). Pressing Enter simply prints ^M. Pressing Ctrl-J does the job.


Leszek Buczkowski

unread,
May 8, 2025, 6:25:55 AMMay 8
to Picat
Correction:

The ^M issue seems to be specific to WezTerm, the terminal app I usually use. It does not occur in other terminal apps (the default macos Terminal, Rio and iTerm2), so this is not really a Picat problem..

Neng-Fa Zhou

unread,
May 8, 2025, 8:36:49 AMMay 8
to Leszek Buczkowski, Picat
Thanks for sharing the information. I also had the same issue with the Apple Clang compiler when I used a Mac with an Intell processor. However, after I switched to MacBook Pro with an m1 processor, the issue disappeared. The version of gcc I use is:

gcc --version
Apple clang version 16.0.0 (clang-1600.0.26.6)

Now compilation of Picat only takes seconds (with the -O3 option). What version of Clang do you use?

Cheers,
NF


--
You received this message because you are subscribed to the Google Groups "Picat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picat-lang+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/picat-lang/33c6dce6-f9e8-416c-80c0-62fa816a0328n%40googlegroups.com.

Leszek Buczkowski

unread,
May 8, 2025, 1:25:31 PMMay 8
to Picat
gcc --version
Apple clang version 17.0.0 (clang-1700.0.13.3)
Target: arm64-apple-darwin24.4.0
Thread model: posix
Reply all
Reply to author
Forward
0 new messages