[Bug rust/111899] [14 regression] GCC fails to bootstrap with 'rust-tree.cc:131:10: error: ‘NON_DEPENDENT_EXPR’ was not declared in this scope'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111899 Sam James changed: What|Removed |Added Component|spam|rust CC||dkm at gcc dot gnu.org, ||gcc-rust at gcc dot gnu.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113056] New: [14 regression] Build failure in libgrust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056 Bug ID: 113056 Summary: [14 regression] Build failure in libgrust Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- This started on this week's snapshot (obviously). I've not analysed it at all yet. ``` /bin/sh /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/gcc-14-20231217/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/14 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/14/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/14 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/14/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/14/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/14/include/g++-v14 --disable-silent-rules --disable-dependency-tracking --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/14/python --enable-languages=c,c++,fortran,rust --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --disable-libunwind-exceptions --enable-checking=yes,extra,rtl --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion=Gentoo Hardened 14.0.0_pre20231217 p11 --with-gcc-major-version-only --enable-libstdcxx-time --enable-lto --disable-libstdcxx-pch --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64 --disable-fixed-point --enable-targets=all --enable-libgomp --disable-libssp --disable-libada --enable-cet --disable-systemtap --enable-valgrind-annotations --disable-vtable-verify --disable-libvtv --with-zstd --with-isl --disable-isl-version-check --enable-default-pie --enable-host-pie --enable-host-bind-now --enable-default-ssp --with-build-config=bootstrap-O3 bootstrap-lto bootstrap-cet [...] checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for style of include used by make... GNU checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/ -B/usr/x86_64-pc-lin ux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32 checking for suffix of object files... configure: error: in `/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/libgrust': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details make[1]: *** [Makefile:16176: configure-libgrust] Error 1 make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build' make[1]: *** Waiting for unfinished jobs [...] ``` and from libgrust's config.log: ``` [...] configure:3271: checking for x86_64-pc-linux-gnu-gcc configure:3298: result: /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/u sr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32 configure:3567: checking for C compiler version configure:3576: /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_6 4-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32 --version >&5 /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/gcc-14-20231217/libgrust/configure: 1: eval: /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc: not found configure:3587: $? = 127 configure:3576: /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_6 4-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32 -v >&5 /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/gcc-14-20231217/libgrust/configure: 1: eval: /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc: not found configure:3587: $? = 127 configure:3576: /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_6 4-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_
[Bug rust/113056] [14 regression] Build failure in libgrust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056 --- Comment #1 from Sam James --- Created attachment 56897 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56897&action=edit config.log (libgrust) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113056] [14 regression] Build failure in libgrust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056 --- Comment #2 from Sam James --- Created attachment 56898 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56898&action=edit build.log.xz -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113056] [14 regression] Build failure in libgrust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056 --- Comment #5 from Sam James --- ftr (given I only gave a packaged build log) repro'd with ./configure --prefix=/tmp/gcc --enable-languages=c,c++,rust --enable-multilib --with-multilib-list=m32,m64 --with-checking=yes,extra,rtl --disable-analyzer --disable-cet --disable-default-pie --disable-default-ssp --disable-gcov --disable-libada --disable-libatomic --disable-libgomp --disable-libitm --disable-libquadmath --disable-libsanitizer --disable-libssp --disable-libstdcxx-pch --disable-libvtv --disable-lto --disable-nls --disable-objc-gc --disable-systemtap --disable-werror && make -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113056] [14 regression] Build failure in libgrust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056 --- Comment #8 from Sam James --- for the pkg build (original report): no for the quick test I did earlier: yes because I was rushing, oops -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113056] [14 regression] Build failure in libgrust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056 --- Comment #10 from Sam James --- (In reply to Sam James from comment #8) > for the pkg build (original report): no > for the quick test I did earlier: yes because I was rushing, oops /tmp/build $ ~/git/gcc/configure --prefix=/tmp/gcc --enable-languages=c,c++,rust --enable-multilib --with-multilib-list=m32,m64 --with-checking=yes,extra,rtl --disable-analyzer --disable-cet --disable-default-pie --disable-default-ssp --disable-gcov --disable-libada --disable-libatomic --disable-libgomp --disable-libitm --disable-libquadmath --disable-libsanitizer --disable-libssp --disable-libstdcxx-pch --disable-libvtv --disable-lto --disable-nls --disable-objc-gc --disable-systemtap --disable-werror && make -j$(nproc) failed for me as well, so out of source indeed fails as well -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113553] rust fails to build on sparc64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553 Sam James changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=112836 --- Comment #4 from Sam James --- Adding PR112836 to See Also because (part of this) involves posix_spawn on sparc. Wonder if Rainer's issue - which I've hit too - is the same as the one I'm seeing on glibc too. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113553] rust fails to build on sparc64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553 --- Comment #7 from Sam James --- (In reply to Sam James from comment #4) (sorry, I misread Rainer's comment - he was talking about glibc too.) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/114629] rust-ast-resolve-expr contains bloated code for funny_error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629 Sam James changed: What|Removed |Added See Also||https://github.com/Rust-GCC ||/gccrs/issues/1996 CC||sjames at gcc dot gnu.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug bootstrap/115453] [15 regression] Noise from new dlopen, pthread configure checks since r15-1177-g75299e4fe50aa8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115453 Sam James changed: What|Removed |Added CC||collin.funk1 at gmail dot com --- Comment #11 from Sam James --- commit r15-1436-gc6a9ab8c920f29 Author: Collin Funk Date: Thu Jun 13 17:53:55 2024 -0700 build: Fix missing variable quotes When dlopen and pthread_create are in libc the variable is set to "none required", therefore running configure will show the following errors: ./configure: line 8997: test: too many arguments ./configure: line 8999: test: too many arguments ./configure: line 9003: test: too many arguments ./configure: line 9005: test: =: unary operator expected gcc/configure also has a similar problem on gcc_cv_as_mips_explicit_relocs: ./gcc/configure: line 30242: test: =: unary operator expected ChangeLog: * configure.ac: Quote variable result of AC_SEARCH_LIBS. * configure: Regenerate. gcc/ChangeLog: * configure.ac: Add missing quotation of variable gcc_cv_as_mips_explicit_relocs. * configure: Regenerate. Signed-off-by: Collin Funk But the crate vs create needs fixing still. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/108087] -Wodr warnings in rust/rust-lang.cc (lang_type)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108087 Sam James changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=116182 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/108087] -Wodr warnings in rust/rust-lang.cc (lang_type)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108087 Sam James changed: What|Removed |Added Target Milestone|--- |14.0 See Also||https://github.com/Rust-GCC ||/gccrs/pull/2586 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Sam James --- I think this was fixed by https://github.com/Rust-GCC/gccrs/pull/2586 -> r14-7947-g9048f08f4e9459. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116187] New: -Wuninitialized warnings in libgrust/libproc_macro_internal/literal.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116187
Bug ID: 116187
Summary: -Wuninitialized warnings in
libgrust/libproc_macro_internal/literal.cc
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rust
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org
Target Milestone: ---
During bootstrap, I noticed:
```
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:
In function ‘make_byte’:
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:196:24:
warning: ‘payload’ is used uninitialized [-Wuninitialized]
196 | return {BYTE, payload};
|^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:195:18:
note: ‘payload’ declared here
195 | LitKindPayload payload;
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:
In function ‘make_char’:
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:203:24:
warning: ‘payload’ is used uninitialized [-Wuninitialized]
203 | return {CHAR, payload};
|^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:202:18:
note: ‘payload’ declared here
202 | LitKindPayload payload;
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:
In function ‘make_integer’:
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:210:27:
warning: ‘payload’ is used uninitialized [-Wuninitialized]
210 | return {INTEGER, payload};
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:209:18:
note: ‘payload’ declared here
209 | LitKindPayload payload;
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:
In function ‘make_float’:
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:217:25:
warning: ‘payload’ is used uninitialized [-Wuninitialized]
217 | return {FLOAT, payload};
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:216:18:
note: ‘payload’ declared here
216 | LitKindPayload payload;
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:
In function ‘make_str’:
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:224:23:
warning: ‘payload’ is used uninitialized [-Wuninitialized]
224 | return {STR, payload};
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:223:18:
note: ‘payload’ declared here
223 | LitKindPayload payload;
| ^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:
In function ‘make_byte_str’:
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:239:28:
warning: ‘payload’ is used uninitialized [-Wuninitialized]
239 | return {BYTE_STR, payload};
|^
/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libgrust/libproc_macro_internal/literal.cc:238:18:
note: ‘payload’ declared here
238 | LitKindPayload payload;
| ^
[...]
```
libgrust/libproc_macro_internal/literal.cc has a bunch of helpers like this:
```
LitKind
LitKind::make_byte ()
{
LitKindPayload payload;
return {BYTE, payload};
}
```
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug rust/116225] New: Rust test failures with -D_GLIBCXX_ASSERTIONS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116225 Bug ID: 116225 Summary: Rust test failures with -D_GLIBCXX_ASSERTIONS Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: testsuite-fail Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- Created attachment 58820 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58820&action=edit rust.log.xz ``` # grep -rsin ^FAIL: gcc/testsuite/rust/rust.log 1634:FAIL: rust/compile/issue-2238.rs (internal compiler error: Aborted) 1635:FAIL: rust/compile/issue-2238.rs at line 13 (test for warnings, line 12) 1636:FAIL: rust/compile/issue-2238.rs (test for excess errors) 2499:FAIL: rust/compile/name_resolution2.rs (internal compiler error: Aborted) 2500:FAIL: rust/compile/name_resolution2.rs (test for warnings, line 7) 2501:FAIL: rust/compile/name_resolution2.rs (test for excess errors) 2588:FAIL: rust/compile/name_resolution4.rs (internal compiler error: Aborted) 2589:FAIL: rust/compile/name_resolution4.rs (test for warnings, line 5) 2590:FAIL: rust/compile/name_resolution4.rs (test for excess errors) 2705:FAIL: rust/compile/non_member_const.rs (internal compiler error: Aborted) 2708:FAIL: rust/compile/non_member_const.rs (test for excess errors) 2831:FAIL: rust/compile/pattern-struct.rs (internal compiler error: Aborted) 2833:FAIL: rust/compile/pattern-struct.rs (test for excess errors) ``` I've attached rust.log, but they're all assertions from -D_GLIBCXX_ASSERTIONS. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116225] Rust test failures with -D_GLIBCXX_ASSERTIONS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116225 --- Comment #1 from Sam James --- e.g. ``` /var/tmp/portage/sys-devel/gcc-15.0./work/build/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/bits/stl_stack.h:293: void std::stack<_Tp, _Sequence>::pop() [with _Tp = unsigned int; _Sequence = std::deque >]: Assertion '!this->empty()' failed. crab1: internal compiler error: Aborted 0x563424577306 internal_error(char const*, ...) /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/diagnostic-global-context.cc:491 0x563423db8d51 crash_signal /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/toplev.cc:321 0x56342588588a std::__glibcxx_assert_fail(char const*, int, char const*, char const*) /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./libstdc++-v3/src/c++11/assert_fail.cc:41 0x56342562c653 std::stack > >::pop() /var/tmp/portage/sys-devel/gcc-15.0./work/build/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/bits/stl_stack.h:293 0x56342562c653 Rust::Resolver::TypeCheckContext::LifetimeResolver::pop_binder() /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/typecheck/rust-hir-type-check.h:350 0x56342562c653 Rust::Resolver::TypeCheckContext::LifetimeResolverGuard::~LifetimeResolverGuard() /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/typecheck/rust-hir-type-check.h:427 0x56342562c653 Rust::Resolver::TypeCheckItem::visit(Rust::HIR::Function&) /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/typecheck/rust-hir-type-check-item.cc:613 0x5634255deff3 Rust::Resolver::TypeCheckItem::Resolve(Rust::HIR::Item&) /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/typecheck/rust-hir-type-check-item.cc:55 0x563425597848 Rust::Resolver::TypeResolution::Resolve(Rust::HIR::Crate&) /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/typecheck/rust-hir-type-check.cc:70 0x563425353b5e Rust::Session::compile_crate(char const*) /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/rust-session-manager.cc:667 ``` -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116225] Rust test failures with -D_GLIBCXX_ASSERTIONS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116225 --- Comment #2 from Sam James --- We should add a -D_GLIBCXX_ASSERTIONS build into the rust CI but we should also really encourage at least one of the CI efforts on gcc-regressions etc to do such a config too. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug middle-end/108102] rust bootstrap comparison failure on s390x-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108102 Sam James changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |13.0 --- Comment #17 from Sam James --- Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116192] [15 regression] 32-bit rust build fails
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116192 Sam James changed: What|Removed |Added See Also||https://github.com/Rust-GCC ||/gccrs/pull/3114, ||https://github.com/Rust-GCC ||/gccrs/pull/3119 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116561] [15 regression] gcc/testsuite/rust/execute/torture/iter1.rs:350:5: internal compiler error: 'verify_gimple' failed since r15-3328-g673a448aa24efedd5ac140ebf7bfe652d7a6a846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116561 Sam James changed: What|Removed |Added Summary|gcc/testsuite/rust/execute/ |[15 regression] |torture/iter1.rs:350:5: |gcc/testsuite/rust/execute/ |internal compiler error:|torture/iter1.rs:350:5: |'verify_gimple' failed |internal compiler error: ||'verify_gimple' failed ||since ||r15-3328-g673a448aa24efedd5 ||ac140ebf7bfe652d7a6a846 CC| |sjames at gcc dot gnu.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116225] Rust test failures with -D_GLIBCXX_ASSERTIONS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116225 Sam James changed: What|Removed |Added See Also||https://github.com/Rust-GCC ||/gccrs/issues/3137, ||https://github.com/Rust-GCC ||/gccrs/pull/3138 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116225] Rust test failures with -D_GLIBCXX_ASSERTIONS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116225 Sam James changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=116951 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116561] [15 regression] gcc/testsuite/rust/execute/torture/iter1.rs:350:5: internal compiler error: 'verify_gimple' failed since r15-3328-g673a448aa24efedd5ac140ebf7bfe652d7a6a846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116561 --- Comment #2 from Sam James --- (In reply to Thomas Schwinge from comment #1) > This appears to be due to recent commit > r15-3328-g673a448aa24efedd5ac140ebf7bfe652d7a6a846 "Optimize initialization > of small padded objects". > > Given this commit doesn't appear to be causing any other issues, chances are > that the Rust front end is doing "something funny"? It seems to have started passing yesterday or so, probably after r15-5772-gf93059c82e61d6. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116225] Rust test failures with -D_GLIBCXX_ASSERTIONS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116225 Sam James changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Target Milestone|--- |15.0 --- Comment #4 from Sam James --- Fixed between 15th and 19th March and there's a CI job for this in the gccrs repo now too. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/116187] -Wuninitialized warnings in libgrust/libproc_macro_internal/literal.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116187 Sam James changed: What|Removed |Added Last reconfirmed||2025-3-25 --- Comment #1 from Sam James --- I thought I'd seen a change fixing this but it looks like no. I can still reproduce it on trunk. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119353] [15 regression] Rust fails to build (build failure: error[E0554]: `#![feature]` may not be used on the stable release channel)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119353 Sam James changed: What|Removed |Added Target Milestone|--- |15.0 Summary|build failure: |[15 regression] Rust fails |error[E0554]: `#![feature]` |to build (build failure: |may not be used on the |error[E0554]: `#![feature]` |stable release channel |may not be used on the ||stable release channel) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119353] [15 regression] Rust fails to build (build failure: error[E0554]: `#![feature]` may not be used on the stable release channel)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119353 --- Comment #1 from Sam James --- What version of rustc? (rustc --version) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119333] [15 regression] Rust bootstrap fails with cargo trying to download polonius crates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333
--- Comment #2 from Sam James ---
.cargo/ at top-level with:
.cargo/config.toml:
```
[net]
offline = true
```
and CARGO_HOME="${srcdir}/.cargo" or something like that would work.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug rust/119508] Hundreds of rust tests XPASS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508 Sam James changed: What|Removed |Added Keywords||testsuite-fail --- Comment #3 from Sam James --- I see it too on x86_64 linux and it seems to flap a bit. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/117869] rust fails to build with cargo command error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117869 --- Comment #3 from Sam James --- Since r15-9083-gd560f3f9594339, 1.49 should work again, but it needs documenting still. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119333] New: [15 regression] Rust bootstrap fails with cargo trying to download polonius crates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333 Bug ID: 119333 Summary: [15 regression] Rust bootstrap fails with cargo trying to download polonius crates Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org, pierre-emmanuel.patry at embecosm dot com Target Milestone: --- On trunk at r15-8235-g051ca98a12908b, I see: ``` cargo build --manifest-path /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/checks/errors/borrowck/ffi-polonius/Cargo.toml --release --target-dir rust/ffi-polonius Updating crates.io index warning: spurious network error (3 tries remaining): [6] Could not resolve hostname (Could not resolve host: index.crates.io) warning: spurious network error (2 tries remaining): [6] Could not resolve hostname (Could not resolve host: index.crates.io) warning: spurious network error (1 tries remaining): [6] Could not resolve hostname (Could not resolve host: index.crates.io) error: failed to get `polonius-engine` as a dependency of package `ffi-polonius v0.1.0 (/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/checks/errors/borrowck/ffi-polonius)` Caused by: download of config.json failed Caused by: failed to download from `https://index.crates.io/config.json` Caused by: [6] Could not resolve hostname (Could not resolve host: index.crates.io) make[3]: *** [/var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.0./gcc/rust/Make-lang.in:506: rust/libffi_polonius.a] Error 101 make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-15.0./work/build/gcc' ``` The build needs to work offline using e.g. vendored crates instead. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119333] [15 regression] Rust bootstrap fails with cargo trying to download polonius crates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333 Sam James changed: What|Removed |Added Target Milestone|--- |15.0 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119333] [15 regression] Rust bootstrap fails with cargo trying to download polonius crates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333 --- Comment #1 from Sam James --- In libgrust/libformat_parser/Makefile.am, we have: ``` # TODO: Improve `cargo` invocation with host specific flags, possibly creating a $(CARGO) variable? $(LIBFORMAT_PARSER): $(srcdir)/Cargo.toml $(srcdir)/src/*.rs cargo \ --config $(srcdir)/.cargo/config \ build \ --offline \ --target-dir . \ --manifest-path $(srcdir)/Cargo.toml \ # FIXME: Not always '--release', right? ``` But nothing passing --offline for gcc/rust/checks/error/borrowck/*. We should really have some global cargo config setting offline. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119333] [15 regression] Rust bootstrap fails with cargo trying to download polonius crates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333 Sam James changed: What|Removed |Added See Also||https://github.com/Rust-GCC ||/gccrs/pull/3504 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119508] Hundreds of rust tests XPASS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508 --- Comment #13 from Sam James --- I'm not seeing it anywhere, and I consistently was before. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/120018] [15/16 regression] internal compiler error: in redirect_to_unreachable, at ipa-fnsummary.cc:258 for 32-bits
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120018 Sam James changed: What|Removed |Added Target Milestone|--- |15.2 Summary|internal compiler error: in |[15/16 regression] internal |redirect_to_unreachable, at |compiler error: in |ipa-fnsummary.cc:258 for|redirect_to_unreachable, at |32-bits |ipa-fnsummary.cc:258 for ||32-bits Keywords||ice-checking, ||ice-on-valid-code -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119508] Hundreds of rust tests XPASS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508 --- Comment #9 from Sam James --- It is, as r15-9287-g89ca1e3cb697a8. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/119508] Hundreds of rust tests XPASS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org See Also||https://github.com/Rust-GCC ||/gccrs/issues/3740 --- Comment #20 from Sam James --- We're discussing further XPASS issues also at https://github.com/Rust-GCC/gccrs/issues/3740. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/108124] Rust: ASAN&UBSAN issues when tests are run
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108124 Sam James changed: What|Removed |Added Blocks||86656, 63426 Keywords||testsuite-fail Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426 [Bug 63426] [meta-bug] Issues found with -fsanitize=undefined https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656 [Bug 86656] [meta-bug] Issues found with -fsanitize=address -- You are receiving this mail because: You are on the CC list for the bug.
[Bug middle-end/120192] Internal compiler error when building ring Rust crate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120192 Sam James changed: What|Removed |Added Component|rust|middle-end See Also||https://github.com/niXman/m ||ingw-builds/issues/706 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug target/120192] Internal compiler error when building ring Rust crate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120192 Sam James changed: What|Removed |Added CC|dkm at gcc dot gnu.org,|sjames at gcc dot gnu.org |gcc-rust at gcc dot gnu.org, | |pierre-emmanuel.patry@embec | |osm.com | -- You are receiving this mail because: You are on the CC list for the bug.
[Bug target/120192] Internal compiler error when building ring Rust crate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120192 --- Comment #4 from Sam James --- (In reply to Sam James from comment #1) > 1) The full command line for GCC (maybe cargo build --verbose will do it, I > don't know) Sorry, I missed this is in the output. Still need preprocessed source though. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug middle-end/120192] Internal compiler error when building ring Rust crate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120192 Sam James changed: What|Removed |Added Keywords||ice-on-valid-code --- Comment #1 from Sam James --- (The Rust component on our Bugzilla is for GCC's WIP Rust frontend.) Could you try to get two things for us please? 1) The full command line for GCC (maybe cargo build --verbose will do it, I don't know) 2) When you have 1), re-run that command with -save-temps and share the preprocessed source file it creates -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113473] rust/compile/iterators1.rs etc. FAIL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113473 Sam James changed: What|Removed |Added Keywords||testsuite-fail -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113472] rust/compile/issue-1446.rs FAILs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113472 Sam James changed: What|Removed |Added Keywords||testsuite-fail -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113477] rust/compile/torture/alt_patterns1.rs FAILs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113477 Sam James changed: What|Removed |Added Keywords||testsuite-fail -- You are receiving this mail because: You are on the CC list for the bug.
