22:54:25drmeisterI'm thinking for optimization we go in a different direction - we implement beach's call site optimization. That works with the faso/fasp files fine.
22:56:03drmeisterWe could do call site optimization to have Common Lisp code call C++ code that takes doubles directly.
22:57:20drmeisterIf we know a C++ function takes a double and we call it from CL and we have the value in an unboxed double - then we can create a call-site that takes it from wherever it is in the CL function and put it in whatever double register the callee needs.
23:07:22drmeisterMy basic point is I think with faso files and call site optimization we can get the kind of performance that we could get with LTO and in a much more flexible/lispy way.
23:07:38drmeisterAnd without the bloat of inlining.
23:22:52Bikethe c++ functions are static, so i would think we can do that without the call site optimization? just generate calls with the unboxed parameters