search for: sentances

Dear all, I am trying to write an R function that can estimate Transfer functions *with additive noise* i.e. Y_t = \delta^-1(B)\omega(B)X_{t-b} + N_t where B is the backward shift operator, b is the delay and N_t is a noisy component that can be modelled as an ARMA process. The parameters to both the impulse response function and the ARMA noisy component need to be estimated simultaneously. I

On Jan 30, 2012, at 10:08 AM, Devang Patel wrote: > > On Jan 27, 2012, at 5:00 PM, Dan Gohman wrote: > >> Not all of these are miscompiles, > > None I'd say, may be TBAA. Then you missed value ranges and fpaccuracy. Anyway, here are some examples of optimizations which aren't implemented yet, but which have been seriously considered: metadata to mark C++ copy

On Jan 30, 2012, at 11:34 AM, Dan Gohman wrote: > Even if we single out TBAA, recall that TBAA was one of the main > motivations for the design of MDNodes -- it's in the second sentance, > and most of the last paragraph, of > http://blog.llvm.org/2010/04/extensible-metadata-in-llvm-ir.html ... and in last paragraph the author says ... "This use of metadata is also safe,

...t place. If I'm reading you correctly, you are relying on exception propagation and handler (destructors for local objects) execution. You have chosen not to add extra exception logic to LLVM itself, but are relying on the correctness of exception propagation within the code. (The last two sentances are intended to be a restatement of what your message said. If I misunderstood, please correct me.) Does this mean that you're compiling your build of LLVM with exceptions enabled? By default, I believe LLVM is built without RTTI or exception support. For the particular cases you mention...

...reading you correctly, you are relying on exception propagation > and handler (destructors for local objects) execution. You have chosen > not to add extra exception logic to LLVM itself, but are relying on the > correctness of exception propagation within the code. (The last two > sentances are intended to be a restatement of what your message said. > If I misunderstood, please correct me.) It was probably not completely correct to say that we did not extend the exception propagation in LLVM. In most of cases where malloc or other C allocation functions are called, we had to a...

Hi Hal, > Does this mean that you're using C++ exception handling to manage the cleanup? No, not really. From the place where we're calling into llvm we are catching all exceptions that may occur during compilation, but normally we do not add any additional catch clauses into the llvm source itself. We mainly rely on correct stack unwinding by destructors in llvm when an exception is

Hi, we have an Debian Etch 4.0 amd64 server with 2 B410P cards. Asterisk SVN r99777 is installed. We tried with mISDN shipped with Asterisk/Zaptel (make b410p) as well as with the latest version from mISDN.org 1.1.7.2. zaptel, ztdummy and crt-ccitt modules are loaded. Output of /dev/zap is: root at SrvPhone:~# ls -al /dev/zap total 0 drwxr-xr-x 2 root root 120 2008-01-23 16:42 .

ripley@stats.ox.ac.uk wrote: > > On Tue, 14 May 2002, Dirk Eddelbuettel wrote: > > > With a (late prerelease of) 1.5.0 on Windows, using sprintf on NaN > > yields garbage when the number of decimal is specified while it > > works fine for NA: > > > > > sprintf("%.2f", NA) > > [1] "0.00" > > I get that on Linux too, but

On Jan 27, 2012, at 5:00 PM, Dan Gohman wrote: > Not all of these are miscompiles, None I'd say, may be TBAA. > but the point is that valid but > naive optimizations can cause them to be actively misleading ... but not cause mis-compilation. Note, optimization passes are free to update info conveyed through MDNodes, if they want to. The "optional to update" while still

On 5 September 2010 19:32, Talin <viridia at gmail.com> wrote: > I've carefully studied the source code of CGDebugInfo in clang as a working > example. One puzzlement is that there's a discrepancy between what the > "source level debugging with LLVM" docs say and what clang does: According > to the docs, DW_TAG_formal_parameter is used to specify a formal

On Jan 27, 2012, at 3:40 PM, Devang Patel wrote: > [ removing cfe-dev from the cc list ] > > On Jan 27, 2012, at 1:31 PM, Dan Gohman wrote: > >> On Jan 27, 2012, at 11:20 AM, Devang Patel wrote: >> >>> >>> On Jan 26, 2012, at 2:10 PM, Dan Gohman wrote: >>> >>>> On Jan 26, 2012, at 12:54 PM, Devang Patel wrote:

1. Large 1 MB I/O, all reads and write to file systems 1MB (can use setvbuf to do this with out coding) e.g a awk programme doing 8K I/O to read 2GB file took 16 min, a perl programme doing 1MB I/O took 16 seconds. 2. When doing rsync -a /dir1/dir2 /dir3/dir4 Do not use pipe's, as they only read/write 5k at a time this is extremly slow, check it out with Solaris truss. Use sockets with

On Sun, Sep 5, 2010 at 1:02 PM, Renato Golin <rengolin at systemcall.org>wrote: > On 5 September 2010 19:32, Talin <viridia at gmail.com> wrote: > > I've carefully studied the source code of CGDebugInfo in clang as a > working > > example. One puzzlement is that there's a discrepancy between what the > > "source level debugging with LLVM" docs

Hi, I''m starting to play with btrfs on my new computer. I''m running Gentoo and have compiled the 2.6.31 kernel, enabling btrfs. Now I have 2 partitions (on 2 different sata disks) that are free for me to play with, each about 375 gb in size. I wanted to create a "raid1" volume using these two partitions, so I did: # mkfs.btrfs -d raid1 /dev/sda5 /dev/sdb5 # mount

Hi all, I am attempting to build samba3 beta2 for AD support, and I've run into a brick wall. I am using Solaris 2.7 and 2.9, with gcc 2.95.2, with krb5-1.2.8 and (now) libiconv-1.9.1 Firstly, I am getting errors of the like: Error loading module '/usr/local/samba/lib/charset/CP850.so': ld.so.1: ./smbclient: fatal: /usr/local/samba/lib/charset/CP850.so: open failed: No such file or

I was discussing with Don about a private topic..and while skimming the code I noticed that during a 'ssh mouring at site ls' the /etc/environment is *ONLY* read if the remote machine is an AIX box. This is undocumented and I'm wondering if someone using AIX could explain WHY it exists in the session.c:do_child()? No other OS has this. I don't see why AIX should require it.

I hate to be a nag, but after several days of working on this I am still utterly stumped. Let me recap the situation as it currently stands: I'm trying to write code that generates DWARF debugging information for my compiler using DIFactory and friends. Unfortunately the information I am generating appears to be invalid, but I can't figure out the cause. Based on the advice in the

Hi all I'm guessing this is a little off topic but here goes... We use PXELINUX and kickstart to automate our RHEL deployments and updates. Recently we started using PXELINUX/memdisk and an MS-DOS image to update the workstation BIOS'es. After selecting <F12> (network boot) and picking the update BIOS option, the BIOS is flashed, BIOS configuration made standard and then the

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these