Test results for gccrs on Debian unstable ia64
Hi! I have started to test gccrs on various targets supported by Debian to see if there are any portability issues with the code. The first target I have tested is Debian unstable ia64. I tested revision fd9e53249c6c269e68f9aca71b3d17b3ecee8e8a. The code builds without any obvious issues and I was able to run the testsuite with the following results: === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/execute/execute.exp ... FAIL: rust.test/execute/block_expr1.rs -O0 execution test FAIL: rust.test/execute/block_expr1.rs -O1 execution test FAIL: rust.test/execute/block_expr1.rs -O2 execution test FAIL: rust.test/execute/block_expr1.rs -O3 -g execution test FAIL: rust.test/execute/block_expr1.rs -Os execution test FAIL: rust.test/execute/block_expr1.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: rust.test/execute/block_expr1.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test FAIL: rust.test/execute/empty_main.rs -O0 execution test FAIL: rust.test/execute/empty_main.rs -O1 execution test FAIL: rust.test/execute/empty_main.rs -O2 execution test FAIL: rust.test/execute/empty_main.rs -O3 -g execution test FAIL: rust.test/execute/empty_main.rs -Os execution test FAIL: rust.test/execute/empty_main.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: rust.test/execute/empty_main.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test FAIL: rust.test/execute/func1.rs -O0 execution test FAIL: rust.test/execute/func1.rs -O1 execution test FAIL: rust.test/execute/func1.rs -O2 execution test FAIL: rust.test/execute/func1.rs -O3 -g execution test FAIL: rust.test/execute/func1.rs -Os execution test FAIL: rust.test/execute/func1.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: rust.test/execute/func1.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/unsupported/unsupported.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/xfail_compile/xfail_compile.exp ... === rust Summary === # of expected passes2347 # of unexpected failures21 # of expected failures 26 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' I will test on more targets throughout the next days. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable powerpc (failure)
Hi! Trying to build revision fd9e53249c6c269e68f9aca71b3d17b3ecee8e8a on 32-bit PowerPC fails with: g++ -c -g -O2 -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -fno-PIE -I. -Ibuild -I../../gcc -I../../gcc/build -I../../gcc/../include -I../../gcc/../libcpp/include \ -o build/genpreds.o ../../gcc/genpreds.c In file included from ./tm.h:32, from ../../gcc/genpreds.c:26: ../../gcc/config/rs6000/linux.h:63:3: error: #error "TARGET_RUST_OS_INFO already defined in linux.h (rs6000) - c++ undefines it and redefines it." 63 | # error "TARGET_RUST_OS_INFO already defined in linux.h (rs6000) - c++ undefines it and redefines it." | ^ ../../gcc/config/rs6000/linux.h:65: warning: "TARGET_RUST_OS_INFO" redefined 65 | #define TARGET_RUST_OS_INFO() \ | In file included from ./tm.h:31, from ../../gcc/genpreds.c:26: ../../gcc/config/rs6000/sysv4.h:554: note: this is the location of the previous definition 554 | #define TARGET_RUST_OS_INFO() \ | make[2]: *** [Makefile:2833: build/genpreds.o] Error 1 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: *** [Makefile:4415: all-gcc] Error 2 make[1]: Leaving directory '/home/glaubitz/gccrs/build' make: *** [Makefile:944: all] Error 2 Reported as [1]. Adrian > [1] https://github.com/Rust-GCC/gccrs/issues/468 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable ia64
Hi Marc! On 6/2/21 2:41 PM, Marc wrote: >> # of expected passes2347 >> # of unexpected failures21 >> # of expected failures 26 > > Would it be possible to have the corresponding .log file ? Looks like > nearly all execution tests are KO (3 out of 4...). Sure, just found the log file. Didn't know that there was one ;). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-ia64.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable ppc64 (big-endian)
Hi! Trying to build revision fd9e53249c6c269e68f9aca71b3d17b3ecee8e8a on 64-bit PowerPC (big-endian) succeeds. The testsuite passes without any issues. Attaching the log file, quick summary below: === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes2368 # of expected failures 26 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-ppc64.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable ia64
Hi Marc! On 6/2/21 3:05 PM, Marc wrote: >> Sure, just found the log file. Didn't know that there was one ;). > > Thanks! Looks like something is missing : > > ./block_expr1.exe: error while loading shared libraries: libunwind.so.7: > cannot open shared object file: No such file or directory Ah, yes, libunwind ;-). > Is libunwind installed ? Not sure why your exe needs it, maybe that's a > particularity of ia64? Yes, gcc explicitly needs libunwind on ia64 unless it's configured to use the internal version. I might be able to fix that myself. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable ia64
Hello! On 6/2/21 3:08 PM, John Paul Adrian Glaubitz wrote: >> Is libunwind installed ? Not sure why your exe needs it, maybe that's a >> particularity of ia64? > > Yes, gcc explicitly needs libunwind on ia64 unless it's configured to use > the internal version. I might be able to fix that myself. Addendum: Building with "--with-system-libunwind" fixes the problem for me (see below). Adrian === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/execute/execute.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/unsupported/unsupported.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/xfail_compile/xfail_compile.exp ... === rust Summary === # of expected passes2368 # of expected failures 26 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable ia64
Hi Marc! On 6/2/21 6:58 PM, Marc wrote: > Thanks for testing this! IIUC, this is an issue on our side, so I'll > open an issue. Let me test a plain GCC build with just C and C++ first to make sure it's not a general GCC problem on ia64. libunwind on ia64 can be a bit tricky sometimes, so it might not be gccrs which is to be blamed here. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable s390x
27; make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-s390x.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable ia64
Hi Marc! On 6/2/21 7:02 PM, Marc wrote: >> libunwind on ia64 can be a bit tricky sometimes, so it might not be gccrs >> which is to be blamed here. > > Ah, sorry, already opened :). I'll close it if needed ! > > https://github.com/Rust-GCC/gccrs/issues/474 Let's keep it open for the time being so it doesn't fall off the table. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable aarch64
Hi! Just built revision 324dfb828cec09f7638b48b6e25e4007b45b9cbc on Debian unstable aarch64. Testsuite passes without any issues, attaching the full log. Adrian === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes2368 # of expected failures 26 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-aarch64.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable aarch64
Hi Phil! On 6/3/21 1:58 PM, Philip Herron wrote: > I just had a thought it would be nice if we could keep a matrix of > different platforms gccrs has been tested on, and they could have states of: > > 1. Build Failure > 2. Test Failures link to log > 3. Tests pass, no unexpected results > > What if we maintained a section in the wiki for this? Sounds like a great idea. I think another idea would be to set up Travis which has support for a couple of architectures such as aarch64 and ppc64le. I'm not planning to keep repeating this manual build and testsuite runs, but I just want to get familiar with the project and fix some minor portability issues while I'm at it. I'm also particularly interested to see how well gccrs already works on various architectures. Getting Rust to work on more targets is very important for Debian as we have some architectures which are currently falling behind due to the lack of platform support in rustc. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable sparc64
Hi! Just built revision 324dfb828cec09f7638b48b6e25e4007b45b9cbc on Debian unstable sparc64. Testsuite passes without any issues, attaching the full log. Adrian === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes2368 # of expected failures 26 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-sparc64.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: GCC Rust monthly call
On 6/4/21 12:47 PM, Philip Herron wrote: > For those interested, you find the meeting notes of our call over on: > https://github.com/Rust-GCC/Reporting/blob/main/2021-06-04-community-call.md Ah, dang, I missed the call. I somehow thought it would be in the evening :|. Next time then. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: GCC Rust monthly call
On 6/4/21 12:54 PM, Philip Herron wrote: > I think my email with the time is not very clear which doesn't help. I will > maybe copy how the risc-v guys put their status report call email out with > examples of timezones and the simple UTC time. > > Have a great day, The next one will be 2nd of July 2021, these meetings are > on the first Friday of the month. Noted, thanks. See you hopefully next time. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable hppa
Hi! Just built revision 325ef69b132819b824ae757695d9724e503f7256 on Debian unstable hppa. Testsuite passes without any issues, attaching the full log. CC'ing the hppa GCC, Kernel and Debian maintainers. Adrian === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes2368 # of expected failures 26 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-hppa.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable m68k
-O2 -flto -fuse-linker-plugin -fno-fat-lto-objects 3 blank line(s) in output FAIL: rust/compile/torture/methods2.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) FAIL: rust/compile/torture/methods3.rs -O0 (internal compiler error) FAIL: rust/compile/torture/methods3.rs -O0 3 blank line(s) in output FAIL: rust/compile/torture/methods3.rs -O0 (test for excess errors) FAIL: rust/compile/torture/methods3.rs -O1 (internal compiler error) FAIL: rust/compile/torture/methods3.rs -O1 3 blank line(s) in output FAIL: rust/compile/torture/methods3.rs -O1 (test for excess errors) FAIL: rust/compile/torture/methods3.rs -O2 (internal compiler error) FAIL: rust/compile/torture/methods3.rs -O2 3 blank line(s) in output FAIL: rust/compile/torture/methods3.rs -O2 (test for excess errors) FAIL: rust/compile/torture/methods3.rs -O3 -g (internal compiler error) FAIL: rust/compile/torture/methods3.rs -O3 -g 3 blank line(s) in output FAIL: rust/compile/torture/methods3.rs -O3 -g (test for excess errors) FAIL: rust/compile/torture/methods3.rs -Os (internal compiler error) FAIL: rust/compile/torture/methods3.rs -Os 3 blank line(s) in output FAIL: rust/compile/torture/methods3.rs -Os (test for excess errors) FAIL: rust/compile/torture/methods3.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none (internal compiler error) FAIL: rust/compile/torture/methods3.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none 3 blank line(s) in output FAIL: rust/compile/torture/methods3.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors) FAIL: rust/compile/torture/methods3.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (internal compiler error) FAIL: rust/compile/torture/methods3.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects 3 blank line(s) in output FAIL: rust/compile/torture/methods3.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) Running /glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes2412 # of unexpected failures105 # of expected failures 15 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-m68k.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Test results for gccrs on Debian unstable sh4
Hi! Just built revision ff4715d79e2c17d270db8b94315aa6b574f48994 on Debian unstable sh4 (SuperH) on my Renesas SH-7785LCR evaluation board. Testsuite passes without any issues, attaching the full log. CC'ing two SuperH-related mailing list in case someone is interested. Adrian === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /srv/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /srv/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /srv/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /srv/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /srv/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes2415 # of expected failures 15 make[2]: Leaving directory '/srv/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/srv/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-sh4.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable sh4
Hi Philip! On 6/11/21 1:25 PM, Philip Herron wrote: >> Nice! Thanks for your efforts, Adrian! >> > > This is pretty neat, what was it like to compile GCC on that board? It's an older board made in the early 2000s, so it has only 600 MHz which meant building gccrs took a little longer. It's the same architecture as used in the Sega Saturn and Sega Dreamcast. FWIW, the J-Core project is working on open source reimplementations of the SuperH architecture which is why this architecture still has a future despite Hitachi/Renesas having lost interest in favor of ARM. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable s390x
Hello! On 6/2/21 9:48 PM, John Paul Adrian Glaubitz wrote: > Just built gccrs revision 59b417323b25072aff2662f1f54f417f7b7ded61 on Debian > unstable s390x. > > The testsuite fails with the following failures. Attaching the log file. As expected, the recent patch by Michael Karcher [1] has fixed the testsuite on s390x as well. I will test m68k later today. Attaching the full log. Adrian > [1] https://github.com/Rust-GCC/gccrs/pull/614 === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/debug/debug.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes3741 # of expected failures 21 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-s390x-new.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable m68k
Hello! On 6/8/21 1:51 PM, John Paul Adrian Glaubitz wrote: > Testsuite fails, errors seem to indicate the same issue with floating numbers > as it > has been observed on 32-bit x86 and s390x [1]. As expected, Michael's patch [1] also fixed the testsuite on m68k. Attaching the log file. Adrian > [1] https://github.com/Rust-GCC/gccrs/pull/614 === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /glaubitz/gccrs/gcc/testsuite/rust/debug/debug.exp ... Running /glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes3741 # of expected failures 21 make[2]: Leaving directory '/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-m68k-new.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Test results for gccrs on Debian unstable hppa
Hello On 6/7/21 10:33 PM, John Paul Adrian Glaubitz wrote: > Just built revision 325ef69b132819b824ae757695d9724e503f7256 on Debian > unstable hppa. > > Testsuite passes without any issues, attaching the full log. Just as for x86, s390x and m68k, the fix by Michael Karcher [1] has fixed the testsuite on hppa which now passes without any failures. Attaching the log file. Adrian > [1] https://github.com/Rust-GCC/gccrs/pull/614 === rust tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/debug/debug.exp ... Running /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ... === rust Summary === # of expected passes3741 # of expected failures 21 make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc' make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc' -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 rust-hppa-new.log.gz Description: application/gzip -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Merge from GCC upstream into GCC/Rust
Hi Thomas! On 9/24/21 10:30, Thomas Schwinge wrote: > As for checking that the configurations that you're testing are still > fine, would you like to do (and/or fix) that before or after me pushing > the merge? I'm fine with testing after the merge and I'll report issues as they show up. Thanks for asking! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Merge from GCC upstream into GCC/Rust
Hi Philipp! On 9/24/21 13:20, Philip Herron wrote: > Thanks for reaching out to continue helping with this Adrian, what is it > like building on some of your systems, does it take a long time? > > It would be nice to track this in some kind of built matrix, would you be > interested in carving out a wiki page over on > https://github.com/Rust-GCC/gccrs/wiki? Or do you have any other ideas? Sure, if you want a matrix with build times, I can create one. I'm currently on vacation and could work on that next week. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Rust front-end patches v4
On 12/6/22 12:03, Richard Biener via Gcc-rust wrote: On Tue, Dec 6, 2022 at 11:11 AM wrote: This patchset contains the fixed version of our most recent patchset. We have fixed most of the issues noted in the previous round of reviews, and are keeping some for later as they would otherwise create too many conflicts with our updated development branch. Similarly to the previous round of patches, this patchset does not contain any new features - only fixes for the reviews of the v3. New features will follow shortly once that first patchset is merged. Once again, thank you to all the contributors who made this possible and especially to Philip Herron for his dedication to the project. Thanks a lot - this is OK to merge now, thanks for your patience and I'm looking forward for the future improvements. Woohooo, finally. Congratulations to everyone involved in this massive effort and thanks a lot for this huge step forward for the Rust community. Can't wait to see this becoming available in the distributions :D. I will make sure we get the frontend enabled in Debian as soon as possible. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Rust front-end patches v4
On 12/6/22 12:40, Arthur Cohen wrote: Can't wait to see this becoming available in the distributions :D. I will make sure we get the frontend enabled in Debian as soon as possible. Haha, I appreciate the enthusiasm :) Please note however that despite the language being in, the compiler is still at an extremely early stage. We are still not able to properly compile Rust code in the version that we target, 1.49. Don't worry, I'm fully aware of that. However, I still consider the inclusion of gccrs into the main gcc code a major step forward as it means the code is exposed to a much broader audience which means it will see more testing. Since Matthias Klose is regularly uploading gcc snapshots to Debian unstable, the gccrs will be compiled and testrun on more than 20 architectures ;-). And I will report back every issue that is discovered this way. To do anything meaningful with the language, you will also need the core library, which again, we cannot compile yet in its 1.49 version. No worries. This is very much an extremely experimental compiler and will still get a lot of changes in the coming weeks and months up until the release. And I'm looking forward to that. Again, thanks everyone for this fantastic effort! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: [PATCH] build: Check for cargo when building rust language
Hello, On Mon, 2024-04-08 at 18:33 +0200, pierre-emmanuel.pa...@embecosm.com wrote: > The rust frontend requires cargo to build some of it's components, > it's presence was not checked during configuration. Isn't this creating a hen-and-egg problem? How am I supposed to build a Rust compiler for a target which is not supported by rustc (yet) when gccrs is supposed to build-depend on cargo which requires rustc? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: [PATCH] build: Check for cargo when building rust language
On Tue, 2024-04-09 at 10:00 +0200, Jakub Jelinek wrote: > On Tue, Apr 09, 2024 at 09:47:18AM +0200, John Paul Adrian Glaubitz wrote: > > Hello, > > > > On Mon, 2024-04-08 at 18:33 +0200, pierre-emmanuel.pa...@embecosm.com wrote: > > > The rust frontend requires cargo to build some of it's components, > > > it's presence was not checked during configuration. > > > > Isn't this creating a hen-and-egg problem? How am I supposed to build a Rust > > compiler for a target which is not supported by rustc (yet) when gccrs is > > supposed to build-depend on cargo which requires rustc? > > Cross-compilers? Well, ok. I had there would be a more convenient solution. I guess we will have to wait for rustc_codegen_gcc to mature then. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
