[llvm-dev] Another possible tracing feature for TableGen

Paul C. Anagnostopoulos via llvm-dev llvm-dev at lists.llvm.org
Thu Aug 13 07:04:59 PDT 2020

Ah, yes, tracing defm's is a whole different thing.

I'm going to start fooling around with this and see what can be done. I'm learning TableGen at the same time, so nothing will happen quickly. Thanks for your encouragement.

At 8/13/2020 08:53 AM, Nicolai Hähnle wrote:

>I like this idea, it's probably more useful than the original one.
>The main challenge that comes to mind is that the final name of the
>record may only be known quite late in the process. Consider a record
>that is the result of a defm in a multiclass, with inheritance added
>at multiple steps on the way. During parsing you don't yet know what
>the final record name is going to be, so it's going to be difficult to
>filter based on that ;)
>That said, I'm curious what you come up with to make it happen. Maybe
>a mode in which *every* record keeps around a bit of data describing
>where it comes from, so that you can then print it selectively?

More information about the llvm-dev mailing list