Sorry for the confusion, we need to do a better job of keeping the
website consistent. Here's the scoop:
LLVM is used only at runtime, specificly within the JIT for lowlevel
optimizations and code generation.
The build options are because using the JIT is optional and therefore
linking against LLVM is optional.
There is some code in rakelib/vm.rake to compile all of the Rubinius C+
+ code using llvm-gcc, but it's entirely seperate from the LLVM usage
within the JIT. This is for like choosing to compile the vm with a
different version of gcc or Intels compiler.
Hope that clears it up a bit!
- Evan // via iPhone
On Mar 8, 2010, at 11:17 AM, Jon <[email protected]> wrote:
What specifically does rubinius require the LLVM infrastructure for?
Required both at build time and runtime?
At least at build time, for JIT enabled VM, that is. Oh wait you
probably already knew that :)
-r
Yeah, understood for build time :)
...although http://rubini.us/docs/getting_started and
http://rubini.us/about/download
conflict on whether LLVM is enabled or disabled by default.
I wasn't looking for a treatise, just a quick drive by from someone
significantly farther up the learning curve...or an RTFM link. Trying
to save a few cycles on setting up a reasonable build and/or runtime
environment.
Jon
--
--- !ruby/object:MailingList
name: rubinius-dev
view: http://groups.google.com/group/rubinius-dev?hl=en
post: [email protected]
unsubscribe: [email protected]
--
--- !ruby/object:MailingList
name: rubinius-dev
view: http://groups.google.com/group/rubinius-dev?hl=en
post: [email protected]
unsubscribe: [email protected]
