public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3532] c++tools : Add a simple handler for ModuleCompiledRequest. Date: Tue, 14 Sep 2021 18:17:58 +0000 (GMT) [thread overview] Message-ID: <20210914181758.C44963858402@sourceware.org> (raw) https://gcc.gnu.org/g:c89d805397f1f09b1a58f01d5cb90211c85a9abc commit r12-3532-gc89d805397f1f09b1a58f01d5cb90211c85a9abc Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sat Apr 24 15:44:34 2021 +0100 c++tools : Add a simple handler for ModuleCompiledRequest. This just replies with "OK". c++tools/ChangeLog: * resolver.cc (module_resolver::ModuleCompiledRequest): Add a simple handler. * resolver.h: Declare handler for ModuleCompiledRequest. Diff: --- c++tools/resolver.cc | 11 +++++++++++ c++tools/resolver.h | 4 ++++ 2 files changed, 15 insertions(+) diff --git a/c++tools/resolver.cc b/c++tools/resolver.cc index edd4624b121..421fdaa55fe 100644 --- a/c++tools/resolver.cc +++ b/c++tools/resolver.cc @@ -307,3 +307,14 @@ module_resolver::IncludeTranslateRequest (Cody::Server *s, Cody::Flags, return 0; } +/* This handles a client notification to the server that a CMI has been + produced for a module. For this simplified server, we just accept + the transaction and respond with "OK". */ + +int +module_resolver::ModuleCompiledRequest (Cody::Server *s, Cody::Flags, + std::string &) +{ + s->OKResponse(); + return 0; +} diff --git a/c++tools/resolver.h b/c++tools/resolver.h index b2f4381b4fa..c1ce9564e7f 100644 --- a/c++tools/resolver.h +++ b/c++tools/resolver.h @@ -96,6 +96,10 @@ public: std::string &include) override; + using parent::ModuleCompiledRequest; + virtual int ModuleCompiledRequest (Cody::Server *s, Cody::Flags Flags, + std::string &Module) override; + private: using parent::GetCMISuffix; virtual char const *GetCMISuffix () override;
reply other threads:[~2021-09-14 18:17 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=20210914181758.C44963858402@sourceware.org \ --to=iains@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).