public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] fixup: parser: Fix bootstrap compile error Date: Sun, 5 Mar 2023 11:41:59 +0000 (GMT) [thread overview] Message-ID: <20230305114159.DFE9C3858C00@sourceware.org> (raw) https://gcc.gnu.org/g:35ab5e3dffa21cba757ff8d128726e80fe588057 commit 35ab5e3dffa21cba757ff8d128726e80fe588057 Author: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com> Date: Wed Mar 1 10:04:04 2023 +0100 fixup: parser: Fix bootstrap compile error The recent changes in the parser bringing the parsing of extern type items also brought a compilation error when boostrapping the compiler. gcc/rust/ChangeLog: * parse/rust-parse-impl.h (Parser::parse_external_type_item): Fix compilation error due to unnecessary move. Signed-off-by: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com> Diff: --- gcc/rust/parse/rust-parse-impl.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/gcc/rust/parse/rust-parse-impl.h b/gcc/rust/parse/rust-parse-impl.h index 63e425e5b83..15effaa1979 100644 --- a/gcc/rust/parse/rust-parse-impl.h +++ b/gcc/rust/parse/rust-parse-impl.h @@ -4013,9 +4013,8 @@ Parser<ManagedTokenSource>::parse_external_type_item (AST::Visibility vis, return nullptr; return std::unique_ptr<AST::ExternalTypeItem> ( - new AST::ExternalTypeItem (std::move (alias_name_tok->get_str ()), - std::move (vis), std::move (outer_attrs), - std::move (locus))); + new AST::ExternalTypeItem (alias_name_tok->get_str (), std::move (vis), + std::move (outer_attrs), std::move (locus))); } // Parses a "type alias" (typedef) item.
reply other threads:[~2023-03-05 11:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230305114159.DFE9C3858C00@sourceware.org \ --to=tschwinge@gcc.gnu.org \ --cc=gcc-cvs@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).