public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rust/108111] New: Rust meets clang Date: Wed, 14 Dec 2022 19:17:38 +0000 [thread overview] Message-ID: <bug-108111-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108111 Bug ID: 108111 Summary: Rust meets clang Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- Since the new Rust code landed in gcc, I thought I'd give it compile with clang. The following 14 warning messages were produced: ./../trunk.d1/gcc/rust/ast/rust-item.h:2186:23: warning: 'as_string' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] ../../trunk.d1/gcc/rust/ast/rust-item.h:2189:16: warning: 'accept_vis' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] ../../trunk.d1/gcc/rust/ast/rust-item.h:2191:12: warning: 'get_locus' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] ../../trunk.d1/gcc/rust/ast/rust-item.h:2196:8: warning: 'mark_for_strip' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] ../../trunk.d1/gcc/rust/ast/rust-item.h:2197:8: warning: 'is_marked_for_strip' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] ../../trunk.d1/gcc/rust/ast/rust-pattern.h:894:12: warning: 'get_locus' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] ../../trunk.d1/gcc/rust/hir/tree/rust-hir-type.h:35:8: warning: private field 'in_parens' is not used [-Wunused-private-field] ../../trunk.d1/gcc/rust/lex/rust-lex.h:156:10: warning: explicitly defaulted move assignment operator is implicitly deleted [-Wdefaulted-function-deleted] ../../trunk.d1/gcc/rust/parse/rust-parse-impl.h:14918:23: warning: operator '?:' has lower precedence than '<<'; '<<' will be evaluated first [-Wparentheses] ../../trunk.d1/gcc/rust/typecheck/rust-substitution-mapper.h:332:19: warning: private field 'concrete' is not used [-Wunused-private-field] ../../trunk.d1/gcc/rust/typecheck/rust-tyty-call.h:140:31: warning: private field 'context' is not used [-Wunused-private-field] ../../trunk.d1/gcc/rust/typecheck/rust-tyty-call.h:83:31: warning: private field 'context' is not used [-Wunused-private-field] /usr/bin/../lib/gcc/x86_64-redhat-linux/12/../../../../include/c++/12/bits/new_allocator.h:181:4: warning: destructor called on non-final 'Rust::TyTy::TypeBoundPredicate' that has virtual functions but non-virtual destructor [-Wdelete-non-abstract-non-virtual-dtor] /usr/bin/../lib/gcc/x86_64-redhat-linux/12/../../../../include/c++/12/bits/stl_construct.h:151:7: warning: destructor called on non-final 'Rust::TyTy::TypeBoundPredicate' that has virtual functions but non-virtual destructor [-Wdelete-non-abstract-non-virtual-dtor] Some, all or none of these might be worth fixing.
next reply other threads:[~2022-12-14 19:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 19:17 dcb314 at hotmail dot com [this message] 2022-12-14 21:46 ` [Bug rust/108111] " dkm at gcc dot gnu.org 2022-12-14 22:22 ` redi at gcc dot gnu.org 2022-12-15 10:44 ` marxin at gcc dot gnu.org 2022-12-15 20:22 ` dkm at gcc dot gnu.org 2024-01-16 17:24 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-108111-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).