Displaying 6 results from an estimated 6 matches for "_parallel_".
Did you mean:
parallel_
2004 Jan 08
0
[LLVMdev] Re: idea 10
...ly the
kernel can create the actual executable for the bytecode, no malicious
bytecode program could run. This assumes that "malicious" is detectable
:)
>
> What should I expand/reformulate?
Nothing at this point. I think I realize where you're coming from now
and agree that _parallel_ computing is a very important next step for
LLVM. Let's see what happens with the current work on synchronization
and threading primitives. These things will be needed to support the
kind of parallelization you're talking about.
>
> Valery.
Best Regards,
Reid.
-------------- next...
2004 Jan 08
4
[LLVMdev] Re: idea 10
> My $0.02 worth on this topic ..
and again |0.02 of mein :-)
> However, I find it unreasonable to expect LLVM to provide
> any features in this area. In order to do anything meaningful,
> LLVM would have to have some kind of awareness of networks
> (typically an operating system concern).
> That seems at odds with the "low level" principles of LLVM.
When I
2004 Jan 08
2
[LLVMdev] Re: idea 10
...LLVM supporting multiple CPU at multiple hosts". Isn't that logical?
> I've toyed with the idea of a Linux kernel module for
> LLVM already. [...]
then even easier to speak :)
> Nothing at this point. I think I realize where you're coming from now
> and agree that _parallel_ computing is a very important next step for
> LLVM. Let's see what happens with the current work on synchronization
> and threading primitives. These things will be needed to support the
> kind of parallelization you're talking about.
Right.
...I almost hear the thoughts from Ch...
2019 Apr 26
0
R 3.6.0 is released
...Time() has been vectorized so arguments path and time
of length greater than one are now supported.
* axis() gets new option gap.axis = NA for specifying a
multiplication factor for the minimal "gap" (distance) between
axis labels drawn. Its default is 1 for labels _parallel_ to the
axis, and 0.25 for perpendicular ones.
Perpendicular labels no longer overlap, fixing bug PR#17384.
* The default method of plot() gains new arguments xgap.axis = NA
and ygap.axis = NA to be passed to the x- and y- axis(..,
gap.axis=*) calls.
* removeSource...
2019 Apr 26
0
R 3.6.0 is released
...Time() has been vectorized so arguments path and time
of length greater than one are now supported.
* axis() gets new option gap.axis = NA for specifying a
multiplication factor for the minimal "gap" (distance) between
axis labels drawn. Its default is 1 for labels _parallel_ to the
axis, and 0.25 for perpendicular ones.
Perpendicular labels no longer overlap, fixing bug PR#17384.
* The default method of plot() gains new arguments xgap.axis = NA
and ygap.axis = NA to be passed to the x- and y- axis(..,
gap.axis=*) calls.
* removeSource...
2019 Apr 26
0
R 3.6.0 is released
...Time() has been vectorized so arguments path and time
of length greater than one are now supported.
* axis() gets new option gap.axis = NA for specifying a
multiplication factor for the minimal "gap" (distance) between
axis labels drawn. Its default is 1 for labels _parallel_ to the
axis, and 0.25 for perpendicular ones.
Perpendicular labels no longer overlap, fixing bug PR#17384.
* The default method of plot() gains new arguments xgap.axis = NA
and ygap.axis = NA to be passed to the x- and y- axis(..,
gap.axis=*) calls.
* removeSource...