Displaying 3 results from an estimated 3 matches for "the_dag".
Did you mean:
the_arg
2020 Aug 04
2
TableGen trace facility
...dd a section to the new guide to explain it. I presume it is the case that this behavior should be publicized.
It also appears to be the case that a record is created and bound to its name before fields are inherited from its superclasses, which is why you can write:
class A <dag d> {
dag the_dag = d;
}
def rec1 : A<(ops rec1)>
Do I understand that correctly?
At 8/4/2020 05:38 PM, Nicolai Hähnle wrote:
>On Tue, Aug 4, 2020 at 11:13 PM Paul C. Anagnostopoulos
><paul at windfall.com> wrote:
>> Yes, I understand the problem. To be more useful, TableGen would have to...
2020 Aug 05
2
TableGen trace facility
...is the case that this behavior should be publicized.
> >
> > It also appears to be the case that a record is created and bound to its
> name before fields are inherited from its superclasses, which is why you
> can write:
> >
> > class A <dag d> {
> > dag the_dag = d;
> > }
> >
> > def rec1 : A<(ops rec1)>
> >
> > Do I understand that correctly?
>
> Almost :)
>
> In reality, this is allowed as a special-case by
> TGParser::ParseIDValue, whose purpose is looking up identifiers. See
> the comment about sel...
2020 Aug 04
3
TableGen trace facility
Yes, I understand the problem. To be more useful, TableGen would have to carry the traces along with the classes and records and (re)display the values while the substitutions are being made.
I'm writing a new Programmer's Guide for TableGen and have been digging into the parse-time versus substitution-time issue. I haven't found a document that makes it clear. Can you give a quick