Csaba Hruska

Results 47 comments of Csaba Hruska

This is related to dynamic pipelines what we don't support yet, but it is on the roadmap. I think you have to stick to a specific texture size for now....

It seems that [CoreToIR's fixFuncs](https://github.com/lambdacube3d/lambdacube-compiler/blob/master/src/LambdaCube/Compiler/CoreToIR.hs#L659-L679) function does not calculate the dependency graph correctly. Instead of a custom implementation it would be better to use [Data.Graph.topSort](http://hackage.haskell.org/package/containers-0.6.0.1/docs/Data-Graph.html#v:topSort).

Other papers I read: - [Patterns of Memory Inefficiency](https://www.researchgate.net/publication/221496338_Patterns_of_Memory_Inefficiency) good high level approach for Java - Xu, G. and Rountev, A., Precise Memory Leak Detection for Java Software Using Container...

Hi, I've refactored the primop handling to use hashmap lookup. Try out the interpreter from this branch: https://github.com/grin-compiler/ghc-whole-program-compiler-project/tree/primop-map/external-stg-interpreter see: https://github.com/grin-compiler/ghc-whole-program-compiler-project/commit/f5e6806a60995e491b8e333d33ec0fa07b1c4867

Well, the interpreter on my machine produces the correct output. Which commit/version are you using?

OK, I could reproduce this bug using the https://github.com/grin-compiler/ext-stg-interpreter-presentation-demos version. Since then I've updated GHC-WPC to GHC 9.0.2 and it fixes this issue. I'll release the update version soon.

Having pure state was the main goal and achievement of the interpreter. This will not be changed for sure because it would ruin readability and simplicity. Haskell simply needs a...

Use staged compilation to make it faster. https://github.com/AndrasKovacs/staged

Please customize the interpreter for your needs. The idea is that one could specialize and refactor the interpreter easily to do experiments without worrying the code quality and instead focusing...

I do not plan to optimize the interpreter further. To me the interpreter should be a high level specification which is right now and it should not have optimization related...