Re: LSP based on GCC

2023-05-31 Thread Alexandre Oliva via Gcc
On May 30, 2023, Paul Smith wrote: > On Mon, 2023-05-29 at 17:16 -0300, Alexandre Oliva via Gcc wrote: >> On May 17, 2023, Arsen Arsenović wrote: >> >> > ISTR Alexandre Oliva (CC added) mentioning leveraging GDB to >> > implement various bits of LSP functionality, such as handling >> > multiple

Re: LSP based on GCC

2023-05-30 Thread Paul Smith
On Mon, 2023-05-29 at 17:16 -0300, Alexandre Oliva via Gcc wrote: > On May 17, 2023, Arsen Arsenović wrote: > > > ISTR Alexandre Oliva (CC added) mentioning leveraging GDB to > > implement various bits of LSP functionality, such as handling > > multiple TUs. > > I recall advancing that suggestio

Re: LSP based on GCC

2023-05-29 Thread Alexandre Oliva via Gcc
On May 17, 2023, Arsen Arsenović wrote: > ISTR Alexandre Oliva (CC added) mentioning leveraging GDB to implement > various bits of LSP functionality, such as handling multiple TUs. This > sounds like a good idea to me (at least at a high level), as it could > lead to the hypothetical GNU toolcha

Re: LSP based on GCC

2023-05-18 Thread Paul Smith
On Thu, 2023-05-18 at 10:52 -0400, Ben Boeckel wrote: > PCH files can "be ignored" in some sense because they can be > recalculated from `#include` files pretty easily. Module files, > however, cannot. This makes it even more important that there be a GCC-based LSP server, if a Clang-based one can

Re: LSP based on GCC

2023-05-18 Thread Ben Boeckel via Gcc
On Thu, May 18, 2023 at 09:25:04 -0400, Paul Smith wrote: > On Wed, 2023-05-17 at 18:38 -0400, Ben Boeckel wrote: > > FWIW, this is only going to get worse with C++ modules. > > There's no reason it should. Of course the right answer is to tell > people to fix their build systems and if they want

Re: LSP based on GCC

2023-05-18 Thread Jason Merrill via Gcc
On Wed, May 17, 2023 at 11:47 AM David Malcolm via Gcc 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 > >

Re: LSP based on GCC

2023-05-18 Thread Paul Smith
On Wed, 2023-05-17 at 18:38 -0400, Ben Boeckel wrote: > > egregious example I'm aware of is that they look for GCC-named > > precompiled headers (.gch), even though the Clang PCH format is > > completely different.  So if Clang (and the LSP servers built on > > it) find a .gch header file they will

Re: LSP based on GCC

2023-05-17 Thread Arsen Arsenović via Gcc
David Malcolm writes: > [...snip...] > 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. > > That patch kit did several things: > (a) adds a new "on the sid

Re: LSP based on GCC

2023-05-17 Thread Ben Boeckel via Gcc
On Wed, May 17, 2023 at 15:48:09 -0400, Paul Smith wrote: > More frustratingly, Clang has made some poor decisions around > "compatibility": they tried to leverage the GNU ecosystem by emulating > GCC features and arguments but sometimes break things. The most Alas, the cost of trying to make a c

Re: LSP based on GCC

2023-05-17 Thread Paul Smith
On Wed, 2023-05-17 at 17:28 +0300, Eli Zaretskii via Gcc wrote: > If there are no current plans for implementing LSP, I hope someone > will work on that soon, given that Emacs can now use it, and because > having a GCC-based LSP implementation will allow people to use their > installed GCC as the b