public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [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=] Date: Thu, 18 Jan 2024 09:05:31 +0000 [thread overview] Message-ID: <bug-113461-4-UHFdE7sbVi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113461-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113461 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|hppa*-*-linux* |hppa*-*-linux*, | |*-*-solaris2.11 CC| |ro at gcc dot gnu.org --- Comment #2 from Rainer Orth <ro at gcc dot gnu.org> --- 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<Rust::Resolver::PathProbeCandidate>::size_type' {aka 'unsigned int'} [-Werror=format=] 968 | rust_debug_loc (expr_locus, "resolved to %lu candidates", candidates.size ()); | ~~^ ~~~~~~~~~~~~~~~~~~ | | | | long unsigned int std::set<Rust::Resolver::PathProbeCandidate>::size_type {aka unsigned int} | %u I'm using the attached patch to fix the build.
next prev parent reply other threads:[~2024-01-18 9:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-17 22:50 [Bug rust/113461] New: " danglin at gcc dot gnu.org 2024-01-18 0:29 ` [Bug rust/113461] " pinskia at gcc dot gnu.org 2024-01-18 9:05 ` ro at gcc dot gnu.org [this message] 2024-01-18 9:06 ` ro at gcc dot gnu.org 2024-01-18 9:10 ` pinskia at gcc dot gnu.org 2024-03-04 4:16 ` law 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-113461-4-UHFdE7sbVi@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).