From: Jason Merrill <jason@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gcc@gcc.gnu.org, "Frank Ch. Eigler" <fche@elastic.org>
Subject: Re: LSP based on GCC
Date: Thu, 18 May 2023 10:28:59 -0400 [thread overview]
Message-ID: <CADzB+2kDrz3wnGfrRv82L=07q+v3Yvs=y12w1uAzhe_5gB+QRg@mail.gmail.com> (raw)
In-Reply-To: <febba5c2bb6b9f45b50b7f0f4b2a2c8ddceefa4f.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
On Wed, May 17, 2023 at 11:47 AM David Malcolm via Gcc <gcc@gcc.gnu.org>
wrote:
> On Wed, 2023-05-17 at 17:28 +0300, Eli Zaretskii via Gcc wrote:
> > Dear GCC developers,
>
> [CCing Frank, re the systemtap LSP implementation]
>
> Hi Eli
>
> > Emacs 29, to be released soon, will come with a built-in client for
> > the LSP protocol. This allows to enhance important Emacs features,
> > such as at-point documentation, on-the-fly diagnostic annotations,
> > finding definitions and uses of program identifiers, enhanced
> > completion of symbols and code, etc., based on capabilities of LSP
> > servers.
>
> Excellent. Do you have a handy link to the specific LSP methods that
> Emacs consumes?
>
> >
> > The Emacs LSP client comes with support for many popular LSP servers
> > OOTB and for all the programming languages supported by Emacs.
> > However, all the available servers for C and C++ languages are based
> > on Clang. AFAIU, this is because GCC does not yet have its own
> > implementation of the LSP. I found this message posted to gcc-
> > patches
> > in 2017:
> >
> > https://gcc.gnu.org/legacy-ml/gcc-patches/2017-07/msg01448.html
> >
> > which described the initial implementation of LSP in GCC, but I seem
> > to be unable to find out what happened with that since then.
> >
> > Are there plans for implementing the LSP in GCC? If so, which GCC
> > version is expected to have this included?
>
> I wrote that prototype, but I haven't touched it since 2017, and I
> already have more than enough other work, alas. I'm happy to help if
> someone wants to pick up the work and finish it.
>
Maybe create a BZ and gcc.gnu.org/projects entry for this work?
Jason
next prev parent reply other threads:[~2023-05-18 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 14:28 Eli Zaretskii
2023-05-17 15:46 ` David Malcolm
2023-05-17 17:10 ` Eli Zaretskii
2023-05-17 21:18 ` Arsen Arsenović
2023-05-29 20:16 ` Alexandre Oliva
2023-05-30 14:33 ` Paul Smith
2023-06-01 1:57 ` Alexandre Oliva
2023-05-18 14:28 ` Jason Merrill [this message]
2023-05-17 19:48 ` Paul Smith
2023-05-17 22:38 ` Ben Boeckel
2023-05-18 13:25 ` Paul Smith
2023-05-18 14:52 ` Ben Boeckel
2023-05-18 15:42 ` Paul Smith
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='CADzB+2kDrz3wnGfrRv82L=07q+v3Yvs=y12w1uAzhe_5gB+QRg@mail.gmail.com' \
--to=jason@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=eliz@gnu.org \
--cc=fche@elastic.org \
--cc=gcc@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: link
Be 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).