Displaying 5 results from an estimated 5 matches for "collusion".
Did you mean:
collision
2002 May 03
2
Does OpenSSH have tcp_wrappers *built-in* or just compatibility?
I was under the impression it was just compatibility, and not actually
built-in, but I thought I'd ask here and just make sure of what I'm
saying. :) TIA.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin at coremetrics.com
"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb
-------------- next part
2010 Apr 30
2
Steve Jobs about theora
I guess you've all read it already, but here it goes:
"All video codecs are covered by patents. A patent pool is being
assembled to go after Theora and other ?open source? codecs now.
Unfortunately, just because something is open source, it doesn?t mean
or guarantee that it doesn?t infringe on others patents. An open
standard is different from being royalty free or open source.
Sent
2008 Mar 27
0
[LLVMdev] Hooking the global symbol resolver
Hi Jonathan,
In the context of a static compiler, I would recommend that you
implement your own “on the side” symbol table in order to track this
state and perform on-demand instantiation as required. It is
worthwhile to consider the LLVM module to be a passive output sink,
not an active object.
The JIT compiler, by contrast, is an active object, cooperating with
its environment via
2008 Mar 27
2
[LLVMdev] Hooking the global symbol resolver
...is what we want to do.
That is: we want to use a continuous compilation strategy, which is
precisely what LLVM is supposedly attempting to achieve.
If we adopt the approach that you suggest, we will end up implementing
our own "generate on demand" infrastructure that has to operate in
collusion with the dynamic loader. We know how to do that, but it is a
moderately dicey business. Basically we have to run a pre-resolver
before we emit code to an LLVM module, after which LLVM will run a
second resolver. I certainly agree that this will work.
But I didn't have in mind originally to vie...
2008 Mar 26
4
[LLVMdev] Hooking the global symbol resolver
Okay, we're starting to dig in, and I've hit a question that will no
doubt seem strange.
Context: BitC is a polymorphic language. Since it has unboxed value
types, our approach to compiling a polymorphic function is to
polyinstantate it -- once for each signature.
The name mangling scheme is both stable and reversible. At the site of
the use occurrence, we can fully determine the mangled