Displaying 3 results from an estimated 3 matches for "spify".
Did you mean:
spiffy
2007 Oct 23
2
[LLVMdev] me being stupid: me vs the llvm codebase...
...an a little like printf...)
doesn't appear much like working like a dynamic compiler is a major design
goal (so I hear, it can be used this way, but this is not the focus).
so, it looks like the design focuses mostly of taking the input modules,
grinding it and mixing it, and doing lots of spify inter-module
optimizations (presumably forming a monolithic output representing the
entire project?...).
very different...
mine is very different, I produce masses of object-modules (in the more
traditional sense), which are linked at runtime, and kept in an in-memory
largely but not complet...
2007 Oct 23
0
[LLVMdev] me being stupid: me vs the llvm codebase...
...; doesn't appear much like working like a dynamic compiler is a major
> design goal (so I hear, it can be used this way, but this is not
> the focus).
>
> so, it looks like the design focuses mostly of taking the input
> modules, grinding it and mixing it, and doing lots of spify inter-
> module optimizations (presumably forming a monolithic output
> representing the entire project?...).
LLVM does work well as a static (offline) compiler, where inter-
procedural optimization and link-time optimization are useful. In
llvm-gcc, link-time optimization ("mixin...
2007 Oct 23
2
[LLVMdev] me being stupid: me vs the llvm codebase...
...> doesn't appear much like working like a dynamic compiler is a major
> design goal (so I hear, it can be used this way, but this is not
> the focus).
>
> so, it looks like the design focuses mostly of taking the input
> modules, grinding it and mixing it, and doing lots of spify inter-
> module optimizations (presumably forming a monolithic output
> representing the entire project?...).
< LLVM does work well as a static (offline) compiler, where inter-
procedural optimization and link-time optimization are useful. In
llvm-gcc, link-time optimization ("mixing...