-
Notifications
You must be signed in to change notification settings - Fork 194
Open
Description
I just took a 10-minute-worth look at the directory structure and a couple of source files. One of my conclusions is that the IR has traces of LLVM-inspired constructs; specifically,
getelementptr. Those of us in the compiler industry know thatgetelementptris a very unique feature of LLVM IR, not present in other IR-like representations (e.g. GIMPLE). See DuckDuckGo search for confirmation.- In the same line, the plain-text notation for IR instructions seems derived from LLVM (see LLVM IR documentation for syntax. This seems to be evident in this comment; also, I could not see
dump()-like routines to print text/plain representation from in-memory IR, so these traces seem to only appear in comments - Use of
va_start,va_end,memcpyas IR-level instrinsics (see here (traces) and here (in LLVM IR reference); or here (sources). Again, this seems to be a very strong indicator of something based off LLVM IR design.
Given all the above, and that the LLVM project is under the Apache License v2.0 with LLVM Exceptions, I think this "work" should, at the very least mention (likely in README.md) that underlying LLMs took 'inspiration' from LLVM, and that LLVM is owned by their respective authors / maintainers.
Looking forward to your replies. Also, as time permits, I'll create additional issues for maybe unrelated topics.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels