[cfe-dev] [analyzer] Retrieving macro expansions in the plist output

[Kristóf Umann via cfe-dev]

That sounds good, but I think dumping the macro expansions as proposed
would be a lot better for our needs as of now.
But then again, why not both after this one?

On 24 Sep 2018 22:49, "Artem Dergachev" <noqnoqneo at gmail.com> wrote:

I mean, not macros but the information on which macros are of interest to
the user.

You know which lines of code were executed, so you can figure out which
macros the user may want to look into.

The downside is that it's a bit counter-intuitive for the user, i.e. it'll
be unobvious why some macros are expanded and others are not.


On 9/24/18 1:31 PM, Kristóf Umann wrote:

Can you elaborate? I've been trying to follow closely the patches and
overall discussion in the analyzer in the last couple of months, but I
don't really see how macro expansions could be acquired from that.

On 24 Sep 2018 21:39, "Artem Dergachev" <noqnoqneo at gmail.com> wrote:

> Mm, actually you may want to use the middle-ground solution of referring
> to George's coverage dumps.
>
> On 9/24/18 9:20 AM, Kristóf Umann wrote:
>
>> > Are you planning to dump *all* macro expansions, or only expansions
>> around diagnostic pieces?
>>
>> Sorry for the late reply -- it simply took *this* long to make a
>> functioning prototype, so I didn't know whether dumping all macro
>> expansions or just the related ones would be up to a simple if branch, or a
>> completely different approach. Right now it looks like (well, its mostly
>> already decided) only related macro expansions will be dumped.
>>
>> I'm planning to upload a patch once I can prettify the current code in
>> the coming days! :)
>>
>> Cheers,
>> Kristóf
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20180924/6d10fe68/attachment.html>