similar to: [LLVMdev] Repository Layout

Dear all, I'm currently applying a mixed model approach to meta analysis using the package metafor. I use the "model.matrix()" function to create dummy variables. The option btt gives me the combined test for the dummies. Problem is, I don't know which indices I have to use, and can't really figure it out from the help file and the examples. I use following code : X <-

Hi, I am quite new to R and in need of some advice. I am trying to conduct a meta regression over a some studies with about 7 mod variables which I have to dummy encode. I have found the following piece of code in the manual for the metafor library: ### manual dummy coding of the allocation factor alloc.random <- ifelse(dat$alloc == "random", 1, 0) alloc.alternate <-

Hi Chris, Is there a compelling reason why llvm-gcc does not always produce natural loops. Is it a code size issue, or are there performance implications as well? I am seeing a simple 'while' loop compiled to an unnatural loop, without any gotos, breaks, or continues. What is the reason for this? Marc On Wed, Feb 11, 2009 at 6:51 PM, Chris Lattner <clattner at apple.com> wrote:

Hi Marc, > Is there a compelling reason why llvm-gcc does not always produce natural > loops. Is it a code size issue, or are there performance implications as > well? I am seeing a simple 'while' loop compiled to an unnatural loop, > without any gotos, breaks, or continues. What is the reason for this? is it already an unnatural loop when it comes out of the gcc parts of

Hi Jens, this series removes the revalidate_disk() function, which has been a really odd duck in the last years. The prime reason why most people use it is because it propagates a size change from the gendisk to the block_device structure. But it also calls into the rather ill defined ->revalidate_disk method which is rather useless for the callers. So this adds a new helper to just

On 2011-08-29 04:21, Kurt Lidl wrote: > While I agree bootstrapping a new mirror from scratch is time and > resource consuming, this can be largely avoided by making a seed > of the svn tree available. (Basically, I think that looks like > a compressed tar file of the svn repository.) Or, a svnadmin dump > of the repo could be made available for the adventurous. Having the same

On Feb 11, 2009, at 1:13 PM, Marc de Kruijf wrote: > I am reviving this thread because I am seeing the same thing > (unnatural loops produced by llvm-gcc), but it is not limited to -O0 > -- I am seeing it for -O2 and -O3 as well. > Some of my research work is relying on LoopInfo to provide loop > information for all loops, but it is missing these loops. Is there > any

Oliver Schneider <gmane at assarbad.net> writes: >>> However, we have official git mirrors of most of the projects on >>> llvm.org, would using them instead of svnsync be an option for you? >> >> Well, if the authoritative source code control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git

I am reviving this thread because I am seeing the same thing (unnatural loops produced by llvm-gcc), but it is not limited to -O0 -- I am seeing it for -O2 and -O3 as well. Some of my research work is relying on LoopInfo to provide loop information for all loops, but it is missing these loops. Is there any work in the pipeline that aims to fix this? Many thanks, Marc On Sat, Jun 21, 2008 at

Done with coccinelle: @@ expression e1, e2, e3; identifier rc; @@ ( rc = device_add_disk(e1, e2, e3); | + /* FIXME: handle error. */ device_add_disk(e1, e2, e3); ) Signed-off-by: Fam Zheng <famz at redhat.com> --- arch/m68k/emu/nfblock.c | 1 + arch/um/drivers/ubd_kern.c | 1 + arch/xtensa/platforms/iss/simdisk.c | 1 + drivers/block/DAC960.c

The race condition is noticed between disk_add() and disk attributes, on virtio-blk hotplug. Userspace listens to the KOBJ_ADD uevent generated in add_disk(). At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. As pointed out by Christoph Hellwig in the specific fix [1], virtio-blk

The race condition is noticed between disk_add() and disk attributes, on virtio-blk hotplug. Userspace listens to the KOBJ_ADD uevent generated in add_disk(). At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. As pointed out by Christoph Hellwig in the specific fix [1], virtio-blk

All, I'm finding the current layout a bit frustrating, not to mention that it breaks all the documentation. We currently have modules laid out like this: llvm/trunk/... llvm/branches/... llvm/tags/... stacker/trunk/... stacker/branches/... stacker/tags/... and similarly for all the other modules (test-suite, java, poolalloc, etc.). Unfortunately, this "standard"

I.e., I see this when I run `git fetch`: ``` $ git fetch -v llvm.org From http://llvm.org/git/llvm = [up to date] master -> llvm.org/master = [up to date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date]

On 2007-06-30, at 18:36, Reid Spencer wrote: > I'm finding the current layout a bit frustrating, not to mention > that it breaks all the documentation. [...] I would rather see it > laid out like this: > > trunk/llvm/... > trunk/stacker/... > trunk/java/... > > branches/llvm/... > branches/stacker/... > branches/java/... > >

Hi Gordon, On Sun, 2007-07-01 at 08:22 -0400, Gordon Henriksen wrote: > On 2007-06-30, at 18:36, Reid Spencer wrote: > > > > I'm finding the current layout a bit frustrating, not to mention > > that it breaks all the documentation. [...] I would rather see it > > laid out like this: > > > > > > > > > trunk/llvm/... > >

On Sep 13, 2012, at 12:00 PM, Mon Ping Wang <monping at apple.com> wrote: >>> In C, integer to point conversions are implementation defined and >>> depends on what the addressing structure of the execution environment >>> is. Given the current definition of ptrtoint and intoptr, I feel that >>> the addressing structure feels like a flat memory model

Hi all, What is the right portable way to save graphics in batch mode? Remarks: 1. Problem is STFWed and RTFMed. In particular a short note about png() is found in R-FAQ. In fact, there were stated that png() is not reliable under Linux in batch mode. 2. savePlot under windows is quite convenient, but not supplied under Linux. 3. pdf() + postscript() < savePlot()

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested

This is an attempt to fix the issue that some disks' sysfs attributes are not ready at the time its KOBJ_ADD event is sent. The symptom is during device hotplug, udev may fail to find certain attributes, such as serial or wwn, of the disk. As a result the /dev/disk/by-id entries are not created. The cause is device_add_disk emits the uevent before returning, and the callers have to create