GCC & G++ randomly unable to compile C/C++ programs
Posted: Sat Aug 08, 2020 5:35 pm
After booting AmigaOS4.1FE on an X1000, sometimes I find that GCC/G++ refuses to compile any C/C++ program. G++ just reports:
assertion "cached == 0" failed: file "../../gcc/libcpp/line-map.c", line 277
cc1plus: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.sf.net/projects/adtools/ for instructions.
While GCC just reports:
assertion "cached == 0" failed: file "../../gcc/libcpp/line-map.c", line 277
cc1: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.sf.net/projects/adtools/ for instructions.
And mostly it seems to fail for the rest of the day, despite hard/soft reboots, but then another day it may work perfectly, despite many hard/soft reboots. But occasionally it will suddenly start working without rebooting, and then continue to work until I *do* reboot!
I haven't yet worked out a pattern, and it's very frustrating, as it means I can't do any software development on OS4.
Any suggestions? Seems like maybe some kind of race condition with the OS or other software, but I have no idea where to look. I tried disabling WB Startup programs & User-Startup progs, without any improvement. Increasing the stack did not help. I am using the "latest" SDK (53.30).
assertion "cached == 0" failed: file "../../gcc/libcpp/line-map.c", line 277
cc1plus: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.sf.net/projects/adtools/ for instructions.
While GCC just reports:
assertion "cached == 0" failed: file "../../gcc/libcpp/line-map.c", line 277
cc1: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.sf.net/projects/adtools/ for instructions.
And mostly it seems to fail for the rest of the day, despite hard/soft reboots, but then another day it may work perfectly, despite many hard/soft reboots. But occasionally it will suddenly start working without rebooting, and then continue to work until I *do* reboot!
I haven't yet worked out a pattern, and it's very frustrating, as it means I can't do any software development on OS4.
Any suggestions? Seems like maybe some kind of race condition with the OS or other software, but I have no idea where to look. I tried disabling WB Startup programs & User-Startup progs, without any improvement. Increasing the stack did not help. I am using the "latest" SDK (53.30).