[COMMITTED] rust_debug: Cast size_t values to unsigned long before printing.
Using %lu to format size_t values breaks 32 bit targets, and %zu is not
supported by one of the hosts GCC aims to support - HPUX
gcc/rust/ChangeLog:
* backend/rust-compile-base.cc (HIRCompileBase::resolve_method_address):
Cast size_t value to unsigned long.
* expand/rust-proc-macro.cc (load_macros): Likewise.
* typecheck/rust-hir-type-check-expr.cc (TypeCheckExpr::visit):
Likewise.
---
gcc/rust/backend/rust-compile-base.cc | 3 ++-
gcc/rust/expand/rust-proc-macro.cc | 2 +-
gcc/rust/typecheck/rust-hir-type-check-expr.cc | 4 ++--
3 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/gcc/rust/backend/rust-compile-base.cc
b/gcc/rust/backend/rust-compile-base.cc
index b4a3685ad93..ae9f6707b72 100644
--- a/gcc/rust/backend/rust-compile-base.cc
+++ b/gcc/rust/backend/rust-compile-base.cc
@@ -965,7 +965,8 @@ HIRCompileBase::resolve_method_address (TyTy::FnType
*fntype,
}
const Resolver::PathProbeCandidate *selectedCandidate = nullptr;
- rust_debug_loc (expr_locus, "resolved to %lu candidates", candidates.size
());
+ rust_debug_loc (expr_locus, "resolved to %lu candidates",
+ (unsigned long) candidates.size ());
// filter for the possible case of non fn type items
std::set filteredFunctionCandidates;
diff --git a/gcc/rust/expand/rust-proc-macro.cc
b/gcc/rust/expand/rust-proc-macro.cc
index e8618485b71..09680733e98 100644
--- a/gcc/rust/expand/rust-proc-macro.cc
+++ b/gcc/rust/expand/rust-proc-macro.cc
@@ -171,7 +171,7 @@ load_macros (std::string path)
if (array == nullptr)
return {};
- rust_debug ("Found %lu procedural macros", array->length);
+ rust_debug ("Found %lu procedural macros", (unsigned long) array->length);
return std::vector (array->macros,
array->macros + array->length);
diff --git a/gcc/rust/typecheck/rust-hir-type-check-expr.cc
b/gcc/rust/typecheck/rust-hir-type-check-expr.cc
index 9dbf657958d..030e5f1b63c 100644
--- a/gcc/rust/typecheck/rust-hir-type-check-expr.cc
+++ b/gcc/rust/typecheck/rust-hir-type-check-expr.cc
@@ -1122,10 +1122,10 @@ TypeCheckExpr::visit (HIR::MethodCallExpr &expr)
auto candidate = *candidates.begin ();
rust_debug_loc (expr.get_method_name ().get_locus (),
- "resolved method to: {%u} {%s} with [%zu] adjustments",
+ "resolved method to: {%u} {%s} with [%lu] adjustments",
candidate.candidate.ty->get_ref (),
candidate.candidate.ty->debug_str ().c_str (),
- candidate.adjustments.size ());
+ (unsigned long) candidate.adjustments.size ());
// Get the adjusted self
Adjuster adj (receiver_tyty);
--
2.42.1
[Bug rust/113461] [14 Regression] rust-proc-macro.cc:174:15: error: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'long long unsigned int' [-Werror=format=]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113461
Rainer Orth changed:
What|Removed |Added
Target|hppa*-*-linux* |hppa*-*-linux*,
||*-*-solaris2.11
CC||ro at gcc dot gnu.org
--- Comment #2 from Rainer Orth ---
I'm seeing the same on 32-bit Solaris/SPARC and x86. On top of that, there's
also
/vol/gcc/src/hg/master/local/gcc/rust/backend/rust-compile-base.cc: In member
function 'tree_node*
Rust::Compile::HIRCompileBase::resolve_method_address(Rust::TyTy::FnType*,
Rust::TyTy::BaseType*, location_t)':
/vol/gcc/src/hg/master/local/gcc/rust/backend/rust-compile-base.cc:968:46:
error: format '%lu' expects argument of type 'long unsigned int', but argument
3 has type 'std::set::size_type' {aka
'unsigned int'} [-Werror=format=]
968 | rust_debug_loc (expr_locus, "resolved to %lu candidates",
candidates.size ());
|~~^
~~
| |
|
| long unsigned int
std::set::size_type {aka unsigned int}
|%u
I'm using the attached patch to fix the build.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug rust/113461] [14 Regression] rust-proc-macro.cc:174:15: error: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'long long unsigned int' [-Werror=format=]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113461 --- Comment #3 from Rainer Orth --- Created attachment 57135 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57135&action=edit Proposed patch Tested on i386-pc-solaris2.11, sparc-sun-solaris2.11, and x86_64-pc-linux-gnu. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113461] [14 Regression] rust-proc-macro.cc:174:15: error: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'long long unsigned int' [-Werror=format=]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113461 --- Comment #4 from Andrew Pinski --- Try after r14-8211-g2341df1cb9b3681bfefe29207887b2b3dc271a95 which was just committed. -- You are receiving this mail because: You are on the CC list for the bug.
Re: [COMMITTED] rust_debug: Cast size_t values to unsigned long before printing.
Arthur Cohen writes:
> Using %lu to format size_t values breaks 32 bit targets, and %zu is not
> supported by one of the hosts GCC aims to support - HPUX
But we do have uses of %zu in gcc/rust already!
> diff --git a/gcc/rust/expand/rust-proc-macro.cc
> b/gcc/rust/expand/rust-proc-macro.cc
> index e8618485b71..09680733e98 100644
> --- a/gcc/rust/expand/rust-proc-macro.cc
> +++ b/gcc/rust/expand/rust-proc-macro.cc
> @@ -171,7 +171,7 @@ load_macros (std::string path)
>if (array == nullptr)
> return {};
>
> - rust_debug ("Found %lu procedural macros", array->length);
> + rust_debug ("Found %lu procedural macros", (unsigned long) array->length);
Not the best way either: array->length is std::uint64_t, so the format
should use
... %" PRIu64 " procedural...
instead.
I've attached my patch to PR rust/113461.
Rainer
--
-
Rainer Orth, Center for Biotechnology, Bielefeld University
Re: [COMMITTED] rust_debug: Cast size_t values to unsigned long before printing.
Hi Rainer,
On 1/18/24 10:13, Rainer Orth wrote:
Arthur Cohen writes:
Using %lu to format size_t values breaks 32 bit targets, and %zu is not
supported by one of the hosts GCC aims to support - HPUX
But we do have uses of %zu in gcc/rust already!
diff --git a/gcc/rust/expand/rust-proc-macro.cc
b/gcc/rust/expand/rust-proc-macro.cc
index e8618485b71..09680733e98 100644
--- a/gcc/rust/expand/rust-proc-macro.cc
+++ b/gcc/rust/expand/rust-proc-macro.cc
@@ -171,7 +171,7 @@ load_macros (std::string path)
if (array == nullptr)
return {};
- rust_debug ("Found %lu procedural macros", array->length);
+ rust_debug ("Found %lu procedural macros", (unsigned long) array->length);
Not the best way either: array->length is std::uint64_t, so the format
should use
... %" PRIu64 " procedural...
instead.
I've attached my patch to PR rust/113461.
Yes, I was talking about this on IRC the other day - if we do run in a
situation where we have more than UINT32_MAX procedural macros in memory
we have big issues. These debug prints will probably end up getting
removed soon as they clutter the output a lot for little information.
I don't mind doing it the right way for our regular prints, but we have
not been using PRIu64 in our codebase so far, so I'd rather change all
those incriminating format specifiers at once later down the line - this
patch was pushed so that 32bit targets could bootstrap the Rust frontend
for now.
Best,
Arthur
Rainer
Re: [COMMITTED] rust_debug: Cast size_t values to unsigned long before printing.
Hi Arthur, > Yes, I was talking about this on IRC the other day - if we do run in a > situation where we have more than UINT32_MAX procedural macros in memory > we have big issues. These debug prints will probably end up getting removed > soon as they clutter the output a lot for little information. makes sense, especially if they break the build once in a while ;-) > I don't mind doing it the right way for our regular prints, but we have not > been using PRIu64 in our codebase so far, so I'd rather change all those > incriminating format specifiers at once later down the line - this patch > was pushed so that 32bit targets could bootstrap the Rust frontend for now. Makes sense: using different styles throughout the codebase only creates confusion. On a related issue: didn't you have some 32-bit host in your CI? I remember having similar issues in the past which could easily be avoided in advance this way. Thanks. Rainer -- - Rainer Orth, Center for Biotechnology, Bielefeld University
[Bug rust/113472] New: rust/compile/issue-1446.rs FAILs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113472 Bug ID: 113472 Summary: rust/compile/issue-1446.rs FAILs Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- Target: sparc-sun-solaris2.11 Since the recent Rust import, a test FAILs on 32 and 64-bit Solaris/SPARC: +FAIL: rust/compile/issue-1446.rs (test for excess errors) Excess errors: /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/issue-1446.rs:8:14: error: no method named 'swap_bytes' found in the current scope [E0599] -- 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 Rainer Orth changed: What|Removed |Added Target Milestone|--- |14.0 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113473] New: rust/compile/iterators1.rs etc. FAIL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113473 Bug ID: 113473 Summary: rust/compile/iterators1.rs etc. FAIL Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- Target: sparc-sun-solaris2.11 Since the recent Rust import, two tests FAIL on 32 and 64-bit Solaris/SPARC in similar ways: +FAIL: rust/compile/iterators1.rs (test for excess errors) Excess errors: /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:235:44: error: mismatched types, expected 'u8' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:246:55: error: mismatched types, expected 'u8' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:235:44: error: mismatched types, expected 'u16' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:246:55: error: mismatched types, expected 'u16' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:235:44: error: mismatched types, expected 'u32' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:246:55: error: mismatched types, expected 'u32' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:235:44: error: mismatched types, expected 'u64' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:246:55: error: mismatched types, expected 'u64' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:235:44: error: mismatched types, expected 'usize' but got '()' [E0308] /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/iterators1.rs:246:55: error: mismatched types, expected 'usize' but got '()' [E0308] FAIL: rust/execute/torture/iter1.rs -O0 (test for excess errors) +UNRESOLVED: rust/execute/torture/iter1.rs -O0 compilation failed to produce executable +FAIL: rust/execute/torture/iter1.rs -O1 (test for excess errors) +UNRESOLVED: rust/execute/torture/iter1.rs -O1 compilation failed to produce executable +FAIL: rust/execute/torture/iter1.rs -O2 (test for excess errors) +UNRESOLVED: rust/execute/torture/iter1.rs -O2 compilation failed to produce executable +FAIL: rust/execute/torture/iter1.rs -O2 -flto (test for excess errors) +UNRESOLVED: rust/execute/torture/iter1.rs -O2 -flto compilation failed to produce executable +FAIL: rust/execute/torture/iter1.rs -O2 -flto -flto-partition=none (test for excess errors) +UNRESOLVED: rust/execute/torture/iter1.rs -O2 -flto -flto-partition=none compilation failed to produce executable +FAIL: rust/execute/torture/iter1.rs -O3 -g (test for excess errors) +UNRESOLVED: rust/execute/torture/iter1.rs -O3 -g compilation failed to produce executable +FAIL: rust/execute/torture/iter1.rs -Os (test for excess errors) +UNRESOLVED: rust/execute/torture/iter1.rs -Os compilation failed to produce executable Excess errors: /vol/gcc/src/hg/master/local/gcc/testsuite/rust/execute/torture/iter1.rs:236:44: error: mismatched types, expected 'u8' but got '()' [E0308] [...] Both tests lack big-endian support. -- 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 Rainer Orth changed: What|Removed |Added Target Milestone|--- |14.0 -- You are receiving this mail because: You are on the CC list for the bug.
Re: [COMMITTED] rust_debug: Cast size_t values to unsigned long before printing.
Hi Arthur,
> On 18 Jan 2024, at 10:30, Arthur Cohen wrote:
> On 1/18/24 10:13, Rainer Orth wrote:
>> Arthur Cohen writes:
>>> Using %lu to format size_t values breaks 32 bit targets, and %zu is not
>>> supported by one of the hosts GCC aims to support - HPUX
>> But we do have uses of %zu in gcc/rust already!
>>> diff --git a/gcc/rust/expand/rust-proc-macro.cc
>>> b/gcc/rust/expand/rust-proc-macro.cc
>>> index e8618485b71..09680733e98 100644
>>> --- a/gcc/rust/expand/rust-proc-macro.cc
>>> +++ b/gcc/rust/expand/rust-proc-macro.cc
>>> @@ -171,7 +171,7 @@ load_macros (std::string path)
>>>if (array == nullptr)
>>> return {};
>>> - rust_debug ("Found %lu procedural macros", array->length);
>>> + rust_debug ("Found %lu procedural macros", (unsigned long)
>>> array->length);
>> Not the best way either: array->length is std::uint64_t, so the format
>> should use
>> ... %" PRIu64 " procedural...
>> instead.
>> I've attached my patch to PR rust/113461.
>
> Yes, I was talking about this on IRC the other day - if we do run in a
> situation where we have more than UINT32_MAX procedural macros in memory we
> have big issues. These debug prints will probably end up getting removed soon
> as they clutter the output a lot for little information.
>
> I don't mind doing it the right way for our regular prints, but we have not
> been using PRIu64 in our codebase so far, so I'd rather change all those
> incriminating format specifiers at once later down the line - this patch was
> pushed so that 32bit targets could bootstrap the Rust frontend for now.
For the sake of completeness, the issue does not just affect 32b hosts; If a
64b host chooses (as Darwin does, so that 32b and 64b targets have the same
representation) to make uint64_t “unsigned long long int”, then %lu breaks
there too.
thanks
Iain
[Bug rust/113477] New: rust/compile/torture/alt_patterns1.rs FAILs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113477 Bug ID: 113477 Summary: rust/compile/torture/alt_patterns1.rs FAILs Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- Target: i386-pc-solaris2.11, sparc-sun-solaris2.11 Since the recent Rust import, one test FAILs on both 32 and 64-bit Solaris/SPARC and x86: +FAIL: rust/compile/torture/alt_patterns1.rs -O0 (test for excess errors) +FAIL: rust/compile/torture/alt_patterns1.rs -O1 (test for excess errors) +FAIL: rust/compile/torture/alt_patterns1.rs -O2 (test for excess errors) +FAIL: rust/compile/torture/alt_patterns1.rs -O2 -flto (test for excess errors) +FAIL: rust/compile/torture/alt_patterns1.rs -O2 -flto -flto-partition=none (test for excess errors) +FAIL: rust/compile/torture/alt_patterns1.rs -Os (test for excess errors) Excess errors: /vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/torture/alt_patterns1.rs:14:62: error: variable 'z' is bound inconsistently across pattern alternatives [E0409] -- 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 Rainer Orth changed: What|Removed |Added Target Milestone|--- |14.0 -- You are receiving this mail because: You are on the CC list for the bug.
Re: [COMMITTED] rust_debug: Cast size_t values to unsigned long before printing.
Hi Rainer, On 1/18/24 10:34, Rainer Orth wrote: Hi Arthur, Yes, I was talking about this on IRC the other day - if we do run in a situation where we have more than UINT32_MAX procedural macros in memory we have big issues. These debug prints will probably end up getting removed soon as they clutter the output a lot for little information. makes sense, especially if they break the build once in a while ;-) I don't mind doing it the right way for our regular prints, but we have not been using PRIu64 in our codebase so far, so I'd rather change all those incriminating format specifiers at once later down the line - this patch was pushed so that 32bit targets could bootstrap the Rust frontend for now. Makes sense: using different styles throughout the codebase only creates confusion. On a related issue: didn't you have some 32-bit host in your CI? I remember having similar issues in the past which could easily be avoided in advance this way. We do have 32 bits runners in the buildbot Mark takes care of, but they were not running bootstrap builds so this was getting ignored as it only produced a warning. Definitely something I want to fix quickly. Thanks. Rainer
Re: [COMMITTED] rust_debug: Cast size_t values to unsigned long before printing.
Hi Iain,
On 1/18/24 12:02, Iain Sandoe wrote:
Hi Arthur,
On 18 Jan 2024, at 10:30, Arthur Cohen wrote:
On 1/18/24 10:13, Rainer Orth wrote:
Arthur Cohen writes:
Using %lu to format size_t values breaks 32 bit targets, and %zu is not
supported by one of the hosts GCC aims to support - HPUX
But we do have uses of %zu in gcc/rust already!
diff --git a/gcc/rust/expand/rust-proc-macro.cc
b/gcc/rust/expand/rust-proc-macro.cc
index e8618485b71..09680733e98 100644
--- a/gcc/rust/expand/rust-proc-macro.cc
+++ b/gcc/rust/expand/rust-proc-macro.cc
@@ -171,7 +171,7 @@ load_macros (std::string path)
if (array == nullptr)
return {};
- rust_debug ("Found %lu procedural macros", array->length);
+ rust_debug ("Found %lu procedural macros", (unsigned long) array->length);
Not the best way either: array->length is std::uint64_t, so the format
should use
... %" PRIu64 " procedural...
instead.
I've attached my patch to PR rust/113461.
Yes, I was talking about this on IRC the other day - if we do run in a
situation where we have more than UINT32_MAX procedural macros in memory we
have big issues. These debug prints will probably end up getting removed soon
as they clutter the output a lot for little information.
I don't mind doing it the right way for our regular prints, but we have not
been using PRIu64 in our codebase so far, so I'd rather change all those
incriminating format specifiers at once later down the line - this patch was
pushed so that 32bit targets could bootstrap the Rust frontend for now.
For the sake of completeness, the issue does not just affect 32b hosts; If a
64b host chooses (as Darwin does, so that 32b and 64b targets have the same
representation) to make uint64_t “unsigned long long int”, then %lu breaks
there too.
thanks
Iain
Thanks for the precision! I'll definitely be more careful moving forward.
Kindly,
Arthur
[Bug rust/113499] New: crab1 fails to link when configuring with --disable-plugin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113499 Bug ID: 113499 Summary: crab1 fails to link when configuring with --disable-plugin Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- With --disable-plugin we probably elide -ldl but crab1 calls dlopen even when plugin support is disabled leading to [ 949s] /home/abuild/rpmbuild/BUILD/gcc-14.0.1+git8231/obj-x86_64-suse-linux/./prev-gcc/xg++ -B/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git8231/obj-x86_64-suse-linux/./prev-gcc/ -B/usr/x 86_64-suse-linux/bin/ -nostdinc++ -B/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git8231/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/src/.libs -B/home/abuild/rpmbuild/BUILD/gcc- 14.0.1+git8231/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/libsupc++/.libs -I/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git8231/obj-x86_64-suse-linux/prev-x86_64-suse-linux/l ibstdc++-v3/include/x86_64-suse-linux -I/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git8231/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/include -I/home/abuild/rpmbuild/BUILD/ gcc-14.0.1+git8231/libstdc++-v3/libsupc++ -L/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git8231/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/src/.libs -L/home/abuild/rpmbuild/BU ILD/gcc-14.0.1+git8231/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/libsupc++/.libs -no-pie -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack -protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -fno-checking -gtoggle -fprofile-generate -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous -unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Wconditionally-supported -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macro s -Wno-overlength-strings -DHAVE_CONFIG_H -no-pie -static-libstdc++ -static-libgcc -L./../libgrust/libproc_macro_internal -o crab1 \ [ 949s] rust/rust-lang.o rust/rust-object-export.o rust/rust-linemap.o rust/rust-diagnostics.o rust/rust-gcc.o rust/rust-token.o rust/rust-lex.o rust/rust-cfg-parser.o rust/rust- parse.o rust/rust-ast.o rust/rust-ast-formatting.o rust/rust-path.o rust/rust-pattern.o rust/rust-ast-fragment.o rust/rust-ast-dump.o rust/rust-ast-collector.o rust/rust-ast-visitor.o r ust/rust-hir-dump.o rust/rust-session-manager.o rust/rust-compile.o rust/rust-mangle.o rust/rust-compile-resolve-path.o rust/rust-macro-expand.o rust/rust-cfg-strip.o rust/rust-expand-v isitor.o rust/rust-ast-builder.o rust/rust-derive.o rust/rust-derive-clone.o rust/rust-derive-copy.o rust/rust-proc-macro.o rust/rust-macro-invoc-lexer.o rust/rust-proc-macro-invoc-lexe r.o rust/rust-macro-substitute-ctx.o rust/rust-macro-builtins.o rust/rust-hir.o rust/rust-hir-map.o rust/rust-attributes.o rust/rust-keyword-values.o rust/rust-abi.o rust/rust-token-con verter.o rust/rust-macro.o rust/rust-ast-lower.o rust/rust-ast-lower-base.o rust/rust-ast-lower-pattern.o rust/rust-ast-lower-item.o rust/rust-ast-lower-expr.o rust/rust-ast-lower-type. o rust/rust-ast-lower-stmt.o rust/rust-rib.o rust/rust-name-resolution-context.o rust/rust-default-resolver.o rust/rust-toplevel-name-resolver-2.0.o rust/rust-early-name-resolver-2.0.o rust/rust-early-name-resolver.o rust/rust-name-resolver.o rust/rust-ast-resolve.o rust/rust-ast-resolve-base.o rust/rust-ast-resolve-item.o rust/rust-ast-resolve-pattern.o rust/rust-ast -resolve-expr.o rust/rust-ast-resolve-type.o rust/rust-ast-resolve-path.o rust/rust-ast-resolve-stmt.o rust/rust-ast-resolve-struct-expr-field.o rust/rust-hir-type-check.o rust/rust-pri vacy-check.o rust/rust-privacy-ctx.o rust/rust-reachability.o rust/rust-visibility-resolver.o rust/rust-pub-restricted-visitor.o rust/rust-privacy-reporter.o rust/rust-tyty.o rust/rust- tyty-util.o rust/rust-tyty-call.o rust/rust-tyty-subst.o rust/rust-typecheck-context.o rust/rust-tyty-bounds.o rust/rust-hir-trait-resolve.o rust/rust-hir-trait-reference.o rust/rust-hi r-type-check-item.o rust/rust-hir-type-check-type.o rust/rust-hir-type-check-struct.o rust/rust-hir-type-check-pattern.o rust/rust-hir-type-check-expr.o rust/rust-hir-type-check-stmt.o rust/rust-hir-type-check-enumitem.o rust/rust-hir-type-check-implitem.o rust/rust-borrow-checker.o rust/rust-bir-builder-expr-stmt.o rust/rust-bir-dump.o rust/rust-hir-dot-operator.o ru st/rust-hir-path-probe.o rust/rust-type-util.o rust/rust-coercion.o rust/rust-casts.o rust/rust-unify.o rust/rust-hir-type-check-base.o rust/rust-autoderef.o rust/rust-substitution-mapp er.o rust/rust-const-checker.o rust/rust-lint-marklive.o rust/rust-lint-unused-var.o rust/rust-readonly-check.o rust/rust-hir
[Bug rust/113499] crab1 fails to link when configuring with --disable-plugin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113499 Richard Biener changed: What|Removed |Added Keywords||build -- You are receiving this mail because: You are on the CC list for the bug.
[Bug rust/113499] crab1 fails to link when configuring with --disable-plugin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113499 --- Comment #1 from Richard Biener --- Note it might also be because the failing build is using glibc-2.31, IIRC newer glibc might include libdl directly (at least that's the case for libpthreads ...) -- You are receiving this mail because: You are on the CC list for the bug.
