Displaying 5 results from an estimated 5 matches for "repaid".
Did you mean:
repair
2002 Jan 09
1
performance considerations
...tting up a linux system on a little toshiba libretto -- p-166,
64 megs, plenty of disk space, though -- and i'm wondering as to the
performance effects were i to apply ext3. i presume that keeping the
journal consumes some finite amount of resources; what i don't know
is whether this is repaid or more than repaid in some other way.
advice?
--
dep
There is sobbing of the strong,
And a pall upon the land;
But the People in their weeping
Bare the iron hand;
Beware the
People weeping
When they bare the iron hand.
2008 Mar 27
1
[LLVMdev] Hooking the global symbol resolver
...odern compilers almost universally
use an invertible scheme today.
I know nothing at all about your language (though I would like to
correct that deficiency), but I am very confident that if an invertible
mangling scheme is possible for you in principle, the time spent to
develop one early will be repaid many times over later.
shap
2009 May 28
1
internal and external debugging [was: [R] step by step debugger in R?]
...ould consider adding them.
Finally, my 2c from experience with 'debug': writing it was very hard work. Debugger-writing seems to be a case where one can one can get *something* working quite quickly-- and then get sucked in to a very long and painful process. The effort I spent has been repaid many times over, but...
Mark Bravington
CSIRO, Hobart, Australia
> >> There is also the debug package [3,4] which does __not__ work with R
> >> internals but rather works with instrumenting tricks at the R level.
> >> debug provides a tcl/tk front-end. It is my underst...
2008 Mar 27
0
[LLVMdev] Hooking the global symbol resolver
"Jonathan S. Shapiro" <shap at eros-os.com> writes:
[snip]
> if (!(sym = llvm_resolve_global(GlobalScope, symName)))
> some_failure_action();
>
> it would now look something like:
>
> sym = llvm_resolve_global(GlobalScope, symName);
> if (!sym && frontend_has_symbol_generator
> && frontend_generate_symbol(symname))
>
2008 Mar 27
2
[LLVMdev] Hooking the global symbol resolver
On Thu, 2008-03-27 at 07:44 -0400, Gordon Henriksen wrote:
> 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.
I think I understand what you