On Mon, 2017-07-24 at 16:04 -0400, David Malcolm wrote:
> We currently capture some source location information in the
> frontends, but there are many kinds of source entity for which we
> *don't*
> retain the location information after the initial parse.
>
> For example, in the C/C++ frontends:
>
Thanks for the explanation (snipped).
* C++: add a fix-it hint to -Wsuggest-final-methods
To answer your call for other ideas below: There are other
suggestions that GCC could offer to help improve code, including
* to add the const qualifier to function pointer and reference
argument
On Thu, 2017-07-27 at 13:51 -0600, Martin Sebor wrote:
> I think this is great. My overall question is: is the new BLT
> representation available in the middle-end?
Given that, err, I'm not freeing it anywhere yet (ahem), the answer is
yes. Although it lives in the "gcc" dir, the generated tre
On Jul 26, 2017, Jim Wilson wrote:
> On 07/24/2017 01:04 PM, David Malcolm wrote:
>> * The LSP implementation is a just a proof-of-concept, to further
>> motivate capturing the extra data. Turning it into a "proper" LSP
>> server implementation would be a *lot* more work, and I'm unlikely to
>>
I think this is great. My overall question is: is the new BLT
representation available in the middle-end? If not, do you
have plans to make it available? (I think it might be especially
useful there, to either accurately highlight the source of
a problem when it's far removed from the problem s
On 07/24/2017 01:04 PM, David Malcolm wrote:
* The LSP implementation is a just a proof-of-concept, to further
motivate capturing the extra data. Turning it into a "proper" LSP
server implementation would be a *lot* more work, and I'm unlikely to
actually do that (but maybe someone on t
