[LLVMdev] PHP Zend LLVM extension (SoC)
nicolas.geoffray at lip6.fr
Thu Apr 24 01:04:58 PDT 2008
Owen Anderson wrote:
> On Apr 24, 2008, at 12:54 AM, Chris Lattner wrote:
>>> LLVM likely won't be able to do type inference for you.
>> I'd put it another way: an existing llvm pass won't do type inference
>> for you. The right way to tackle this is to write an language-
>> specific pass on LLVM IR that knows your runtime and can propagate
>> types around.
The thing is, LLVM IR performs type checking when it's being constructed
(e.g BinaryOperator::CreateAdd(A, B) checks A->type == B->type or
BinaryOperator::CreateFDiv(A,B) checks if A is floating point, B is
floating point and A->type == B->type). That's a stopper for performing
type inference on the LLVM IR. To perform type inference on the IR, one
1) Setting the arguments of a function as Opaque (or something like
that, at least something that is able to be redefined later)
2) IR construction: no type check, no type-oriented instructions (eg no
3) Add some meta-information on each instruction (is that the Annotation
4) Perform the type inference.
5) Perform type checking.
> Or just do it at the Zend bytecode level.
I think that's currently the only solution. However:
A) Suppose you don't have a bytecode for your language or you would like
to directly transform your language to LLVM IR. You don't want to end up
creating an instruction set which would be very similar to LLVM IR.
That's highly time and memory consuming since you're creating new
objects for your personal instruction set, very similar to LLVM IR
objects. (I may be thinking too much about JIT here, since it's less a
problem with static compilation).
B) This is the kind of pass that many languages will need, and everyone
performing its own is not very consistent with LLVM philosophy ;-)
I'm not saying 1) to 5) are the right steps to achieve this. But I do
think we need the LLVM IR to get some high-level type information for
type inference or even for type-based optimizations such as type-based
> The meta-point is that performing that kind of optimization requires
> higher level knowledge than what is explicitly represented in the LLVM
> IR. To obtain it, you either need to optimize at a higher level or
> write an LLVM optimization that encodes language-specific high-level
> knowledge. Either approach will work, and it's your call which one is
> easier for you to write.
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the llvm-dev