search for: arg0

...)*c, +, b*c} bar((pixel_idx + 2) * c); // {(a*b+2)*c, +, b*c} bar((pixel_idx + 3) * c); // {(a*b+3)*c, +, b*c} } } and LSR produced void foo(float *input, int a, int b, int c, int n) { * int arg3 = (a * b + 3) * c;* * int arg2 = (a * b + 2) * c;* * int arg1 = (a * b + 1) * c;* * int arg0 = a * b * c;* for (int node_x = 0; node_x < n; ++node_x) { bar(arg0); bar(arg1); bar(arg2); bar(arg3); arg0 += b * c; arg1 += b * c; arg2 += b * c; arg3 += b * c; } } (with obvious redundant operations, i.e. a * b and b * c, combined). Note that the order of a...

...e there any 'magic' numbers in the pass that can be tweaked? Thanks, Frank ; ModuleID = '<stdin>' target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128" target triple = "x86_64-unknown-linux-gnu" define void @main(i64 %lo, i64 %hi, float* noalias %arg0, float* noalias %arg1, float* noalias %arg2) { entrypoint: %0 = getelementptr float* %arg1, i64 64 %1 = getelementptr float* %arg2, i64 64 %2 = getelementptr float* %arg0, i64 64 %3 = bitcast float* %arg1 to <4 x float>* %4 = bitcast float* %0 to <4 x float>* %5 = bit...

...expriority ept vpid I use LLVM 3.6 checked out yesterday ~/toolchain/install/llvm-3.6/bin/opt -datalayout -basicaa -slp-vectorizer -instcombine < func_4x4x4_scalar_p_scalar.ll -S the output goes like: ; ModuleID = '<stdin>' define void @main(i64 %lo, i64 %hi, float* noalias %arg0, float* noalias %arg1, float* noalias %arg2) { entrypoint: %0 = bitcast float* %arg1 to <4 x float>* %1 = load <4 x float>* %0, align 4 %2 = bitcast float* %arg2 to <4 x float>* %3 = load <4 x float>* %2, align 4 %4 = fadd <4 x float> %3, %1 %5 = bit...

...es in as a function argument with only natural alignment (float*). This x86 instruction requires the memory address to be 16 byte aligned which 88 plus something aligned to 4 byte isn't. Here the according IR code which was produced from the SLP vectorizer: define void @func(float* noalias %arg0, float* noalias %arg1, float* noalias %arg2) { entrypoint: ... %104 = getelementptr float* %arg0, i32 22 ... %204 = bitcast float* %104 to <4 x float>* store <4 x float> %198, <4 x float>* %204 This in itself not wrong. However, shouldn't the lowering pass recognize...

...nsnoop and execsnoop etc. My interest is to write a simple script that can snoop the files which uses the 3 syscalls like open,create,unlink. I have gone through dtrace oneliners that can do the same : dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0));}'' dtrace -n ''syscall::creat*:entry { printf("%s %s",execname,copyinstr(arg0));}'' dtrace -n ''syscall::unlink*:entry { printf("%s %s",execname,copyinstr(arg0));}'' But how to write a single script that can snoop & list the...

I have a probe: pid111::myfunc:entry { self->arg = arg0; } pid111::myfunc:return /self->arg/ { @[self->arg] = quantize(); } works great, but i''d like arg0 to be printed in hex. I''ve tried numerous approaches to do this but i''ve hit a wall every time. I''ve tried: 1) self->arg = sprintf(arg0); no, cuz d...

On 7 August 2014 17:33, Chad Rosier <mcrosier at codeaurora.org> wrote: > You might consider filing a bug (llvm.org/bugs) requesting a flag, but I > don't know if the code owners want to expose such a flag. I'm not sure that's a good idea as a raw access to that limit, as there are no guarantees that it'll stay the same. But maybe a flag turning some

Howdy, I was playing around with the malloc/free D script provided by Philip Beevers: http://www.opensolaris.org/jive/thread.jspa?threadID=4224&tstart=15 And decided to change the free:entry probe from: pid24169::free:entry / sz[arg0] / { printf("Freeing %p (size %d)\n", arg0, sz[arg0]); sz[arg0] = 0; } to: pid24169::free:entry / ! sz[arg0] / { printf("[ * ] A bad function is Freeing memory at address %p\n",arg0); ustack(); } When I created a test program [1] and attempted to run the n...

...F offset 76 dtrace: error on enabled probe ID 6 (ID 14: syscall::open:entry): invalid address (0xff34e000) in predicate at DIF offset 28 I don''t know how to interpret these error messages. Below is some D-program codes: . . syscall::open:entry /!progenyof($pid) && copyinstr(arg0) == "/opt/SUNWvts/bin/sparcv9/../../lib/sparcv9/libvtstest.so.1"/ { stop(); system("qtracepid.d %d %s &", pid, basename(copyinstr(arg0))); } . . syscall::open:entry /!loaded[copyinstr(arg0)] && !progenyof($pid) && copyinstr(arg0) == "/opt/SUNWv...

...b/net/bridge/br_ioctl.c --- a/net/bridge/br_ioctl.c 2004-05-20 10:51:05 -07:00 +++ b/net/bridge/br_ioctl.c 2004-05-20 10:51:05 -07:00 @@ -27,14 +27,43 @@ ? jiffies_to_clock_t(timer->expires - jiffies) : 0; } -int br_ioctl_device(struct net_bridge *br, unsigned int cmd, - unsigned long arg0, unsigned long arg1, unsigned long arg2) +/* called with RTNL */ +static int get_bridge_ifindices(int *indices, int num) { - if (br == NULL) - return -EINVAL; + struct net_device *dev; + int i = 0; - switch (cmd) - { + for (dev = dev_base; dev && i < num; dev = dev->next) { + if...

Hi all, Is there some documentation or some example on how to interpret the arg0 .. arg<n> for the aioread, aiowrite, aiowait syscalls? The system call name for all three seems to be "kaio". Michael === Michael Mueller ================== Tel. + 49 8171 63600 Fax. + 49 8171 63615 Web: http://www.michael-mueller-it.de ======================================

.../" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body> <greetMe xmlns="http://web2.web/"> <arg0 xsi:type="xsd:string">Olivier</arg0> </greetMe> </SOAP-ENV:Body> </SOAP-ENV:Envelope> The R commands used are: library("SSOAP") smg8TestService <- SOAPServer("smg8.ulb.ac.be", "/web2/TestService", 8080) contentGreet <-...

It's not caused by "the insertion point is set to the default after". I should mention the reason somewhere earlier. "Reversing the order of arg0~3 is not intentional. The user list of pixel_idx happens to have pixel_idx+3, pixel_idx+2, and pixel_idx+1 in this order, so LSR simply follows this order when collecting the LSRFixups." I'm not an expert on uselist orders, but after skimming Duncan Smith's recent work on preserving u...

I''ve been trying to get access to a userland string that''s behind a second level pointer using DTrace, but I can''t seem to get it to work. I started with the example on the Team DTrace Tips and Tricks slides: trace(copyinstr(*(uintptr_t *)copyin(arg0, curpsinfo->pr_dmodel == PR_MODEL_ILP32 ? 4 : 8))); And when I couldn''t get it to work, I started breaking it down into smaller pieces to see what was going on at each step. Here''s the "C" and "D" code: --- pt.c --- static int sz = sizeof(char *); ma...

...when alloca is "called", or its the same as putting "%z = alloca" in the beggining? or... if alloca is in a loop, the stack grows every time it iterates?? 2) does the LLVM optimizes this: ; this code (arg -> var) is very similar to what gcc generates define void @foo(i32 %arg0) { entry: %var0 = alloca i32 store i32 %arg0, i32* var0 ... %x = load i32* %var0 .... ; never more stores to %var0 or pass it to any function } to something like: define void @foo(i32 arg0) { entry: ; no alloca .... %x = %arg0 .... } does it??? I'm ask...

Whilst trying out some D to get an insight into what is the most common reason for a given function to return, I have bumped into an error I don''t understand. The first take on what I was trying to do was: # dtrace -n ''fbt:ip:ip_input:return{@home[arg0] = count();}'' and all was well. The next step was: # dtrace -n ''fbt:ip::return{@home[strjoin(probefunc,(string)arg0)] = count();}'' but the output was not quite so friendly: dtrace: description ''fbt:ip::return'' matched 1653 probes dtrace: error on ena...

.... I am talking about a double* pointer and like to explicitly overestimate the alignment. I am trying to add this pointer as a function's argument, so that later aligned (vector-) loads would get generated. See the pseudo code of what I try to accomplish: define void @foo( double* noalias %arg0 ) { // switching to C style for( int outer=0 ; outer < end ; ++outer ) { for( int inner=0 ; inner < 4 ; ++inner ) { arg0[ outer*4 + inner ] += arg0[ outer*4 + inner ]; } } The loop vectorizer does its job on the 'inner' loop and generates vector loads/adds/stores for...

...values: > > provider adv { > probe myprobe(int64_t messageId); > }; > > These values are not correctly visible in the dtrace script. > In theory the following dtrace script should work: > > adv$1:::myprobe > { > printf("\n%016llx", arg0); > } > > In reality this only works if the application process which uses the > trace point > is compiled as 64 bit process. > When compiling the application as 32bit process, the input parameter > "messageId" > is transferred to parameters arg0 and arg1. &g...

With dtrace, I can use function arguments in the form of arg0, arg1, etc, as indices into an "associative" array. If all that an array takes as an index is an int64_t, is there any reason for dtrace to require me to have an explicit type conversion in there rather than having it do it for me automatically? At present I need to do: mblks[arg0] or m...

I have samba 3.0.4 acting as a local master browser and couple of win xp sp1, sp2, win 9x client machines. Everything works fine excepts win xp sp2. It just disappears from network neighborehood in about 15-20 minutes after start. stop/starting "Server" system service on this machine solves problem for next 15-20 mins. %) What can be done about it? Is there any sence to upgrade samba to