OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Programming => Topic started by: Paul Smedley on December 07, 2022, 12:17:07 am
-
...due sometime next year..
https://www.phoronix.com/news/GCC-Modula-2-Ready
https://www.phoronix.com/news/GCC-Rust-v4-Cleared-For-Landing
When the GCC 13 code gets closer to release, I'll look at building it, noting that GCC 13 will drop support for STABS debug code, so we won't be able to built debug code....
-
What about one of the debug formats that Open Watcom supports?
-
What about one of the debug formats that Open Watcom supports?
dwarf output should work, but not sure it can be encapsulated into aout object files, and tools like emxomf will certainly choke on it....
-
What about one of the debug formats that Open Watcom supports?
dwarf output should work, but not sure it can be encapsulated into aout object files, and tools like emxomf will certainly choke on it....
With luck, the patch removing stabs can be easily reversed.
-
Yes that will be the initial plan....
-
https://www.phoronix.com/news/Module-2-GCC-Merged
-
https://www.phoronix.com/news/Module-2-GCC-Merged
Reading that reminds me, have you had a chance to look any more at GO support?
-
Hey Andy,
https://www.phoronix.com/news/Module-2-GCC-Merged
Reading that reminds me, have you had a chance to look any more at GO support?
Not recently, but it's a good point - I should take another look. I forget now what the issues were when I last tried enabling it!
Cheers,
Paul
-
Go seemed to build ok, but when it tries to compile code, it fails with:
libtool: compile: U:/DEV/gcc-os2/host-i686-pc-os2-emx/gcc/gccgo -BU:/DEV/gcc-os2/host-i686-pc-os2-emx/gcc/ -B/usr/local1220/i686-pc-os2-emx/bin/ -B/usr/local1220/i686-pc-os2-emx/lib/ -isystem /usr/local1220/i686-pc-os2-emx/include -isystem /usr/local1220/i686-pc-os2-emx/sys-include -minline-all-stringops -g -D__EMX__ -DEMX -DOS2 -D__ST_MT_ERRNO__ -O2 -march=pentium -mtune=pentium4 -static-libgcc -I . -c -fgo-pkgpath=internal/goarch ../.././libgo/go/internal/goarch/goarch.go zgoarch.go
go1.exe: internal compiler error: in go_write_export_data, at go/go-backend.cc:108
libbacktrace could not find executable to open
Please submit a full bug report, with preprocessed source (by using -freport-bug).
See <https://gcc.gnu.org/bugs/> for instructions.
go/go-backend.cc:108 as:
gcc_assert (targetm_common.have_named_sections);
emx.h has:
#define TARGET_HAVE_NAMED_SECTIONS false
So this assertion will always fail.
I don't think a.out supports named sections?? Edit: https://sourceware.org/binutils/docs/as/Section.html seems to confirm...
-
...due sometime next year..
https://www.phoronix.com/news/GCC-Modula-2-Ready
https://www.phoronix.com/news/GCC-Rust-v4-Cleared-For-Landing
When the GCC 13 code gets closer to release, I'll look at building it, noting that GCC 13 will drop support for STABS debug code, so we won't be able to built debug code....
The M2 integration was supposed to happen with GCC12 (and funnily enough with GCC 0.x as well), so I am not holding my breath ...
-
M2 has been merged, so will be in gcc 13..
-
Just thought of another problem with the lack of stabs support, Dmik hacked the Mozilla build system to get the symbols for xul.dll from the stabs info.