search for: predicatible

Hi, I''m a nub in dtrace, could you please help me to find the mistake? I need to implement the logic: - if PID and TID are defined, fire the probe for the particular thread of particular process; - if only PID is defined, fire the probe for the process including all threads. The predicat [i]syscall:::entry / (pid == PID && tid == TID )[/i] / works ok and return syscall for

Assume an architecture that has multiple condition code registers, e.g., powerpc. Now assume that there are predicate instructions like thumb2, but can specify which condition code register they refer to. Now also assume that these predicate instructions themselves are predicatible, if executed they change the current predication state. Can LLVM handle multiple levels of predication? When is IfConversion used and when is EarlyIfConversion used? Is there any documentation on this? thanks, brian

Hi, I've got an ageing NT4 server on our NT4 domain. The hardware is getting unreliable and few people use it. Unfortunately/predicatably the few people who use it are senior staff and they have some (important, naturally) Excel spreadsheets which link to files on this server by name. As I haven't been entirely successful in weening them off this server I've been keeping it ticking

This commit works for me, but TBH I'm not clear on what the actual purpose of this test is supposed to be. Rich.

On 5/20/20 7:50 AM, Richard W.M. Jones wrote: > The old test relied on issuing an asynchronous command to a qemu-io > subprocess, requiring a sleep to ensure that the command had been > carried out. ‘sleep 1’ was not long enough on s390x as you can see > from this partial trace: Nice analysis. > Here are still connecting to nbdkit from "connection A", long after >

Hi all, Does anyone know where I can get a new MacOS X package with puppet...? The newest one on reductivelabs site is 0.23.0... -- Med venlig hilsen Juri Rischel Jensen Fab:IT ApS Vesterbrogade 50 DK-1620 København Tlf: 70 202 407 / Fax: 33 313 640 www.fab-it.dk / juri@fab-it.dk

The old test relied on issuing an asynchronous command to a qemu-io subprocess, requiring a sleep to ensure that the command had been carried out. ‘sleep 1’ was not long enough on s390x as you can see from this partial trace: + exec + qemu-io -f raw nbd:unix:/tmp/tmp.jqOZGj6dnX + exec + echo 'Reading from connection A, try 1' Reading from connection A, try 1 +

Hi Pekka, > How I see it, the data parallel input simply makes the vectorizer's job > easier (skip some of the legality checks) while reusing most of the > implementation (e.g. cost estimation, unrolling decisions, the > vector instruction formation itself, predication/if-conversion, > speculative execution+blend, etc.). > What you need is outer loop vectorization while

[NOTE: I'm new to this list and this is my first approach to OpenSSH code.] I've enhanced "--with-prngd-port=PORT" flag to accept an optional hostname as in "myhost:myport", e.g.: % ./configure --with-prngd-port=example.com:12345 Although I'm certain that this may cause big trouble if remote gatherer isn't online (ssh will refuse to open any connection) I

Hello, I have been running multiple exec scripts that could run in parallel. Does puppet run as much as possible in parallel? If it does not, is there a way to specify that actions may be run in parallel? Also, is puppet a multiple or single thread application? Thank you, -- Rob -- ____________________________________________________________________________________ Sucker-punch spam

On 01/25/2013 09:56 AM, Nadav Rotem wrote: > Thanks for checking the Loop Vectorizer, I am interested in hearing your > feedback. The Loop Vectorizer does not fit here. OpenCL vectorization is > completely different because the language itself is data-parallel. You > don't need all of the legality checks that the loop vectorizer has. I'm aware of this and it was my point in