[llvm-dev] Another possible tracing feature for TableGen

Paul C. Anagnostopoulos via llvm-dev llvm-dev at lists.llvm.org
Mon Aug 10 11:24:12 PDT 2020

Since I started a new thread for this idea rather than continuing the previous TableGen tracing thread, I'm replying to invite a few other people to view this thread, in case they missed it.

At 8/9/2020 12:36 PM, Madhur Amilkanthwar wrote:
>I don't think it's on wrong track in fact it is definitely a step in right direction :) We can definitely improvise it over the time but the idea sounds good to me.
>+1 from my side. 
>On Sun, Aug 9, 2020, 10:03 PM Paul C. Anagnostopoulos via llvm-dev <<mailto:llvm-dev at lists.llvm.org>llvm-dev at lists.llvm.org> wrote:
>I had another idea for a TableGen tracing feature and would like some feedback. It's quite possible I'm on the wrong track here and that improved backend tracing is what folks really need.
>The idea is to add a -trace option to the tblgen command line. With it you can list one or more record names. TableGen would produce a detailed trace of how the record is built: class inheritances, template argument values, surrounding let substitutions, record field values, etc.  An anonymous record could be traced once you knew its name.
>It might make sense to include a trace level, too, since a fully detailed trace might sometimes show too much information. 

More information about the llvm-dev mailing list