Displaying 20 results from an estimated 10000 matches similar to: "Recycling memory with a small free list"
2015 Feb 19
0
Recycling memory with a small free list
On Wed, Feb 18, 2015 at 7:19 AM, Radford Neal <radford at cs.toronto.edu> wrote:
>> ... with assignments inside of loops like this:
>>
>> reweight = function(iter, w, Q) {
>> for (i in 1:iter) {
>> wT = w * Q
>> }
>> }
>> ... before the RHS is executed, the LHS allocation would be added
>> to a small fixed length list of available
2015 Feb 19
1
Recycling memory with a small free list
On Wed, 18 Feb 2015, Nathan Kurz wrote:
> On Wed, Feb 18, 2015 at 7:19 AM, Radford Neal <radford at cs.toronto.edu> wrote:
>>> ... with assignments inside of loops like this:
>>>
>>> reweight = function(iter, w, Q) {
>>> for (i in 1:iter) {
>>> wT = w * Q
>>> }
>>> }
>>> ... before the RHS is executed, the
2015 Feb 18
3
Recycling memory with a small free list
> ... with assignments inside of loops like this:
>
> reweight = function(iter, w, Q) {
> for (i in 1:iter) {
> wT = w * Q
> }
> }
> ... before the RHS is executed, the LHS allocation would be added
> to a small fixed length list of available space which is checked
> before future allocations. If the same size is requested before the
> next garbage
2010 Nov 04
1
orphan inodes deleted issue
Dear All,
My servers running on CentOS 5.5 x86_64 with kernel 2.6.18.194.17.4.el
gigabyte motherboard and 2 harddisks (seagate 500GB).
My CentOS box configured RAID 1, yesterday and today I had the same
problem on 2 servers with same configuration. See the following error
messages for details:
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during
2007 Dec 04
2
weighted Cox proportional hazards regression
I'm getting unexpected results from the coxph function when using
weights from counter-matching. For example, the following code
produces a parameter estimate of -1.59 where I expect 0.63:
d2 = structure(list(x = c(1, 0, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1,
1, 0, 0, 1, 0, 1, 0, 1, 0, 1), wt = c(5, 42, 40, 4, 43, 4, 42,
4, 44, 5, 38, 4, 39, 4, 4, 37, 40, 4, 44, 5, 45, 5, 44, 5), riskset =
2003 May 26
1
portupgrade issue
I am running 4.8-STABLE.
I recently did a cvsup (repeatedly, most recently today). Ever since,
portupgrade dies with the following messages:
zircon# portupgrade -r pkgconfig
/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:310:in `deorigin': failed to
convert nil into String (PkgDB::DBError)
from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:903:in
`tsort_build'
from
2010 Jan 19
1
Model frame when LHS is cbind (PR#14189)
The model frame shows the response and predictors in a data frame with
nicely labelled columns:
fm <- lm(wt~qsec+log(hp)+sqrt(disp), data=mtcars)
model.frame(fm) # ok
When the left hand side consists of more than one response, those response
variables still look good, inside a matrix:
fm <- lm(cbind(qsec,hp,disp)~wt, data=mtcars)
model.frame(fm)[[1]] # ok
A problem arises when
2009 Dec 21
1
Clean up of nv40_context->state.hw and nv40_screen->state
Hi,
I'm trying to find a place where objects held in
nv40_context->state.hw[] and nv40_screen->state[] are being unreferenced
during pipe_context destruction.
Currently I'm observing that these objects are not unreferenced and
since they hold reference to buffer objects, the buffer objects
themselves are not unreferenced as well (for example color buffer or z
buffer).
In
2018 Aug 30
0
ROBUSTNESS: x || y and x && y to give warning/error if length(x) != 1 or length(y) != 1
I have to agree with Emil here. && and || are short circuited like in C and
C++. That means that
TRUE || c(TRUE, FALSE)
FALSE && c(TRUE, FALSE)
cannot give an error because the second part is never evaluated. Throwing a
warning or error for
c(TRUE, FALSE) || TRUE
would mean that the operator gives a different result depending on the
order of the objects, breaking the symmetry.
2011 Jun 11
0
problems with geom_vline, histograms, scale=free and facets in ggplot
Dear list,
I?m having a little trouble with adding vertical lines to a histogram.
I need to draw a matrix of histograms (using facets), and in each
histogram add a vertical line indicating the mean value of the data in
each facet. According to the last example in the geom_hline help, to
display different lines in each facet I need to provide a data frame.
I modified this example to make a plot
2019 Nov 01
3
[PATCH] v2v: Optimize convert for images with small holes
"qemu-img convert" detects zeroes in allocated areas and punch holes in
the destination image. This may save space on the destination image, but
slows down conversion when using outputs such as rhv-upload, which have
very large overhead per requests.
Using the -S flag, we can treat small areas filled with zeroes as data,
limiting the number of requests, and speeding the operation.
Here
2012 May 21
0
[LLVMdev] APInt::sdivrem error?
OK, the code for sdivrem in APInt.h is wrong.
Here's what's written:
static void sdivrem(const APInt &LHS, const APInt &RHS,
APInt &Quotient, APInt &Remainder) {
if (LHS.isNegative()) {
if (RHS.isNegative())
APInt::udivrem(-LHS, -RHS, Quotient, Remainder);
else
APInt::udivrem(-LHS, RHS, Quotient, Remainder);
Quotient =
2011 Sep 22
0
[LLVMdev] Need help in converting int to double
Hi Sarath,
It would have really helped if you had removed the commented out code and inlined the calls to your homemade helper functions before sending it...
You are doing this, in LLVM IR:
%0 = getelementptr %Value* %firstArg, i32 0 ; i8**
%1 = load i8** %0 ; i8*
%2 = bitcast i8* %1 to i64*
%3 = getelementptr %Value* %secondArg, i32 0 ; i8**
%4 = load i8** %3; i8*
%5 = bitcast i8* %4 to i64*
2013 Feb 18
0
Small suggestion for termplot
Brian,
I used termplot(..., plot=FALSE) recently in R-devel: works like a charm. Thanks much
for the update.
Our in-house "gamterms" function, which this obviates, would also return the "constant"
attribute from the underlying predict(..., type="terms") call. I have occasionally found
this useful, and so it would be a worthwhile addition to termplot.
2011 Sep 22
1
[LLVMdev] Need help in converting int to double
Yeah, that's the fault...got the answer...... Thanks James for the help...
Struggling with this for so many days.......
On Thu, Sep 22, 2011 at 4:02 PM, James Molloy <James.Molloy at arm.com> wrote:
> Hi Sarath,****
>
> ** **
>
> It would have really helped if you had removed the commented out code and
> inlined the calls to your homemade helper functions before
2011 Sep 13
1
[LLVMdev] Setting priority in instruction selection
> -----Original Message-----
> From: Eli Friedman [mailto:eli.friedman at gmail.com]
> Sent: Monday, September 12, 2011 7:15 PM
> To: Villmow, Micah
> Cc: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] Setting priority in instruction selection
>
> On Mon, Sep 12, 2011 at 6:53 PM, Villmow, Micah <Micah.Villmow at amd.com>
> wrote:
> > I am having a problem
2011 Sep 22
2
[LLVMdev] Need help in converting int to double
On Thu, Sep 22, 2011 at 3:46 PM, sarath chandra <sarathcse19 at gmail.com>wrote:
> Hi James,
>
> First i converted the void * to int* and then did FPToSI...then did SHL...(
> because CreateShl only accepts integers... i pointer casted it to int64 type
> first)... Below is the code snippet....
>
>
> lhs = mBuilder.CreateStructGEP(firstArg, 0);
> lhs =
2019 Jun 14
2
memory leak in vhost_net_ioctl
Hello Syzbot
On Fri, 14 Jun 2019 02:26:02 +0800 syzbot wrote:
>
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered crash:
> memory leak in vhost_net_ioctl
>
Oh sorry for my poor patch.
> ANGE): hsr_slave_1: link becomes ready
> 2019/06/13 18:24:57 executed programs: 18
> BUG: memory leak
> unreferenced object 0xffff88811cbc6ac0
2019 Jun 14
2
memory leak in vhost_net_ioctl
Hello Syzbot
On Fri, 14 Jun 2019 02:26:02 +0800 syzbot wrote:
>
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered crash:
> memory leak in vhost_net_ioctl
>
Oh sorry for my poor patch.
> ANGE): hsr_slave_1: link becomes ready
> 2019/06/13 18:24:57 executed programs: 18
> BUG: memory leak
> unreferenced object 0xffff88811cbc6ac0
2016 Sep 14
2
undef * 0
Hi,
> Both A and B are undef:
> LHS = (undef & undef) | (undef & undef) = undef // Since ~undef =
undef
> RHS = undef
> Thus transform is correct.
LLVM documentation (http://llvm.org/docs/LangRef.html#undefined-values)
suggests that
it is unsafe to consider (a & undef = undef) and (a | undef = undef).
"As such, it is unsafe to optimize or assume