Displaying 20 results from an estimated 4000 matches similar to: "per sync size limit"
2009 Oct 06
0
[ao] Two patches for libao2
Hi Heikki,
So libao is currently not maintained upstream. In the appropriate IRC
channels I'm lead to believe that there are better libraries out there
that should be used instead.
If so many debian packages didn't link against it I would seriously
consider dropping it all together.
It doesn't sound like it's worth anyone's time maintaining libao
properly upstream. I do have
2001 Dec 03
2
Bug in rsyncd 2.5.0 while handling config file string values
I compiled and tried rsync 2.5.0 but could not get the server
running. loadparm.c:string_set() now calls free() which it did not do
in 2.4.6 and this free() tries to free memory that was not allocated
with malloc.
Here is a gdb run (done after adding return before fork() in
become_daemon) which shows where it crashes and what my minimal config
file for demonstrating the bug was. The config file
2012 Dec 11
1
[LLVMdev] Loads/Stores and MachineMemOperand
The code itself makes sense, but I want to know if this breaks any
guarantee made about preserving a Value* in the MachineMemOperand. It
sounds like we're having the same issue. We were using the Value* stored
in the MachineMemOperand to get address space information during assembly
printing. The alternative is carrying around a lot of extra (redundant)
information in the SDAG.
If it is
2010 Oct 01
2
[LLVMdev] Illegal optimization in LLVM 2.8 during SelectionDAG? (Re: comparison pattern trouble - might be a bug in LLVM 2.8?)
On 1 Oct 2010, at 13:35, Bill Wendling wrote:
> On Sep 30, 2010, at 2:13 AM, Heikki Kultala wrote:
>
>> Bill Wendling wrote:
>>> On Sep 29, 2010, at 12:36 AM, Heikki Kultala wrote:
>>>
>>>> On 29 Sep 2010, at 06:25, Heikki Kultala wrote:
>>>>
>>>>> Our architecture has 1-bit boolean predicate registers.
>>>>>
2010 Oct 04
2
[LLVMdev] Illegal optimization in LLVM 2.8 during SelectionDAG
Bill Wendling wrote:
> On Sep 30, 2010, at 2:13 AM, Heikki Kultala wrote:
>
>> Bill Wendling wrote:
>>> On Sep 29, 2010, at 12:36 AM, Heikki Kultala wrote:
>>>
>>>> On 29 Sep 2010, at 06:25, Heikki Kultala wrote:
>>>>
>>>>> Our architecture has 1-bit boolean predicate registers.
>>>>>
>>>>> I've
2010 Oct 01
0
[LLVMdev] Illegal optimization in LLVM 2.8 during SelectionDAG? (Re: comparison pattern trouble - might be a bug in LLVM 2.8?)
On Sep 30, 2010, at 2:13 AM, Heikki Kultala wrote:
> Bill Wendling wrote:
>> On Sep 29, 2010, at 12:36 AM, Heikki Kultala wrote:
>>
>>> On 29 Sep 2010, at 06:25, Heikki Kultala wrote:
>>>
>>>> Our architecture has 1-bit boolean predicate registers.
>>>>
>>>> I've defined comparison
>>>>
>>>> def
2012 Mar 05
0
[LLVMdev] commit r152019 broke architectures with more than 255 registers
On Mar 5, 2012, at 5:39 AM, Heikki Kultala wrote:
> Our architecture(TCE) can have LOTS of registers.
>
> It seems r152019 changed some register bookkeeping data structures to
> 8-bit. This broke support for architectures with >255 registers.
>
> Please revert this change or make those register-related values at least
> 16 bits wide.
I agree. We can limit the number
2010 Sep 29
0
[LLVMdev] comparison pattern trouble - might be a bug in LLVM 2.8?
On Sep 29, 2010, at 12:36 AM, Heikki Kultala wrote:
> On 29 Sep 2010, at 06:25, Heikki Kultala wrote:
>
>> Our architecture has 1-bit boolean predicate registers.
>>
>> I've defined comparison
>>
>> def NErrb : InstTCE<(outs I1Regs:$op3), (ins I32Regs:$op1,I32Regs:$op2), "", [(set I1Regs:$op3, (setne I32Regs:$op1, I32Regs:$op2))]>;
2010 Sep 30
4
[LLVMdev] Illegal optimization in LLVM 2.8 during SelectionDAG? (Re: comparison pattern trouble - might be a bug in LLVM 2.8?)
Bill Wendling wrote:
> On Sep 29, 2010, at 12:36 AM, Heikki Kultala wrote:
>
>> On 29 Sep 2010, at 06:25, Heikki Kultala wrote:
>>
>>> Our architecture has 1-bit boolean predicate registers.
>>>
>>> I've defined comparison
>>>
>>> def NErrb : InstTCE<(outs I1Regs:$op3), (ins I32Regs:$op1,I32Regs:$op2), "", [(set
2004 May 03
1
A crash (PR#6849)
Dear Sir
There is a acces violation erron (Null pointer) when I have done this. This is
repetable but not inmutable.
0. I have put the command "library("Rcmdr")" in the .Rprofile
1. Start R, load module Rcmdr, Input a dataset in RCommander, then save the
workspace. I can do any analysis now, no crashes, everything works file but
when:
2. I start abain R. It comes up with
2000 Dec 12
1
[Fwd: R code and robust regression]
-------------- next part --------------
An embedded message was scrubbed...
From: Hella Heikki <Heikki.Hella at bof.fi>
Subject: R code and robust regression
Date: Tue, 12 Dec 2000 12:12:14 +0200
Size: 2187
Url: https://stat.ethz.ch/pipermail/r-help/attachments/20001212/c3361c7d/attachment-0001.mht
2011 Sep 29
0
[LLVMdev] r140697 broke building with shared library enabled
On Thu, Sep 29, 2011 at 9:39 AM, Renato Golin <rengolin at systemcall.org>wrote:
> On 29 September 2011 13:54, Justin Holewinski
> <justin.holewinski at gmail.com> wrote:
> > Did you try to re-run configure after pulling that commit?
> > I just tried a shared build with:
> > ../configure --enable-optimized --enable-assertions
> > --enable-targets=host,ptx
2008 Aug 18
2
ifelse
I find it slightly surprising, that
ifelse(TRUE, character(0), "")
returns NA instead of character(0).
[WNT 2.6.2 Patched]
--
Heikki Kaskelma
2001 Dec 03
0
Socket address problems with 2.5.1pre1
The problem shows in the following log snippet. The numeric address of
the peer (localhost in this case) is garbage.
rsyncd[32671]: reverse name lookup failed
rsyncd[32671]: rsync: forward name lookup for failed: Name or service not known
rsyncd[32671]: rsync on debian/ from UNKNOWN (::10fa:ffbf:a426:608%5)
rsyncd[32671]: wrote 616 bytes read 70 bytes total size 143069
I am using linux
2014 Jun 06
2
[LLVMdev] how to turn off conversion of add's into or's (in address calculations)
It seems some optimization pass converts some address computation add's
into or's when it knows it's allowed due correct alignment.
How do I turn this off keep the address calculations as adds?
2010 Sep 29
1
[LLVMdev] comparison pattern trouble - might be a bug in LLVM 2.8?
On 29 Sep 2010, at 06:25, Heikki Kultala wrote:
> Our architecture has 1-bit boolean predicate registers.
>
> I've defined comparison
>
>
> def NErrb : InstTCE<(outs I1Regs:$op3), (ins I32Regs:$op1,I32Regs:$op2), "", [(set I1Regs:$op3, (setne I32Regs:$op1, I32Regs:$op2))]>;
>
>
>
>
> But then I end up having the following bug:
>
>
2002 May 13
4
Help please... rsync 2.5.5 on Solaris 2.7
Hi all, I have just re-joined the list. I have been using Rsync on my
Linux servers for a number of years now without fault. I now have the
need to Rsync data between two Solaris 2.7 servers.
This has got me stumped... Hoping that someone might have a quick answer
for me?
bash-2.03$ rsync -auvvvz sydney:/sun /sun
opening connection using remsh sydney
rsync --server --sender -vvvulogDtprz . /sun
2012 Oct 30
0
[LLVMdev] how to define extending vector load patterns?
Hi Heikki,
> just using [(set V2I32Regs:$result, (sextloadv2i8 ADDRrr:$address))]
>
> gives me error that extloav2i8 is not defined.
I don't have a target to test this on, but looking at
include/llvm/Target/TargetSelectionDAG.td, there is an "sextloadvi8"
PatFrag, at least. I'd suggest a pattern along the lines of:
(set V2I32Regs:$result, (v2i32 (sextloadvi8
2003 Dec 16
3
default --rsh
On Mon, Dec 15, 2003 at 10:51:08AM -0800, Wayne Davison wrote:
> On Mon, Dec 15, 2003 at 10:03:28AM -0800, jw schultz wrote:
>
> > The one thing i really would have liked to have seen in a version bump
> > would have been changing the default remote shell to ssh instead of
> > rsh/remsh.
>
> I can see this being both a good thing (since I think it is a better
>
2002 Apr 23
3
rsync hanging (Sun -> AIX)
I'm trying to rync working between the UK (Sun box) and India (AIX box) and
am having a real problems getting it up and running because every time I do
a full transfer it hangs. The Sun box is the one holding the canonical
source which we want to mirror.
I've been shipped to the India office to get this working and have tried
hundreds of things over the last week, I've also scoured