search for: bla1

Please send patches to llvm-commits not llvm-dev. Writing FileCheck tests has pitfalls. A test along these lines: bla0 CHECK:bla1 will actually pass, because the CHECK pattern is also part of the input so it will readily match itself. You want the CHECK lines not to match themselves, which you can easily do by introducing {{}} into the (middle of the) pattern. That is: bla0 CHECK:{{bla1}} will still pass (incorrectly), w...

Hi, this patch fixes a problem with leading/trailing whitespace matching for FileCheck --strict-whitespace --match-full-lines. Consider a text file: ... $ cat DUMP bla1 bla2 bla3 bla4 bla5 ... with some leading and trailing spaces, made more visible like this: ... $ sed 's/ /_/g' DUMP bla1 bla2 _bla3 bla4_ _bla5_ ... and a FileCheck file CHECK to match DUMP: ... $ cat CHECK // CHECK-LABEL:bla1 // CHECK-NEXT:bla2 // CHECK-NEXT: bla3 // CHECK-NEXT:bla4...

...] [FileCheck] Fix --strict-whitespace --match-full- > lines > > On 14/12/16 18:48, Robinson, Paul wrote: > > Please send patches to llvm-commits not llvm-dev. > > > > Writing FileCheck tests has pitfalls. A test along these lines: > > > > bla0 > > CHECK:bla1 > > > > will actually pass, because the CHECK pattern is also part of the input > > so it will readily match itself. You want the CHECK lines not to match > > themselves, which you can easily do by introducing {{}} into the (middle > > of the) pattern. That is: >...

On 14/12/16 18:48, Robinson, Paul wrote: > Please send patches to llvm-commits not llvm-dev. > > Writing FileCheck tests has pitfalls. A test along these lines: > > bla0 > CHECK:bla1 > > will actually pass, because the CHECK pattern is also part of the input > so it will readily match itself. You want the CHECK lines not to match > themselves, which you can easily do by introducing {{}} into the (middle > of the) pattern. That is: > > bla0 > CHECK:{{bl...

Hi, this patch adds a --verbose option to FileCheck. [ An alternative name could be --debug or --debug-pattern. ] Consider a file CHECK: ... // CHECK-LABEL:bla1 // CHECK-NEXT:bla2 // CHECK-NEXT: bla3 // CHECK-NEXT:bla4 // CHECK-NEXT: bla5 ... and a FileCheck command using --verbose: ... $ echo | FileCheck CHECK --strict-whitespace --match-full-lines --verbose ... For each check the actual match pattern used is shown: ... CHECK:1:16: note: RegEx string ma...

+jyknight, who added --match-full-lines On 12/14/16 5:25 AM, Tom de Vries wrote: > Hi, > > this patch adds a --verbose option to FileCheck. [ An alternative name > could be --debug or --debug-pattern. ] > > Consider a file CHECK: > ... > // CHECK-LABEL:bla1 > // CHECK-NEXT:bla2 > // CHECK-NEXT: bla3 > // CHECK-NEXT:bla4 > // CHECK-NEXT: bla5 > ... > > and a FileCheck command using --verbose: > ... > $ echo | FileCheck CHECK --strict-whitespace --match-full-lines --verbose > ... > > For each check the actual match pa...

...lines > > > On 12/14/16 5:25 AM, Tom de Vries wrote: > > Hi, > > > > this patch adds a --verbose option to FileCheck. [ An alternative name > > could be --debug or --debug-pattern. ] > > > > Consider a file CHECK: > > ... > > // CHECK-LABEL:bla1 > > // CHECK-NEXT:bla2 > > // CHECK-NEXT: bla3 > > // CHECK-NEXT:bla4 > > // CHECK-NEXT: bla5 > > ... > > > > and a FileCheck command using --verbose: > > ... > > $ echo | FileCheck CHECK --strict-whitespace --match-full-lines -- > verbose &g...

...Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 6893 0 DENY_NONE 0x19b RDWR NONE /export/storage smbshare/bla/bla1.docx Server1: Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 2004 0 DENY_WRITE 0x2019f RDWR NONE...

...itespace --match-full- >> lines >> >> On 14/12/16 18:48, Robinson, Paul wrote: >>> Please send patches to llvm-commits not llvm-dev. >>> >>> Writing FileCheck tests has pitfalls. A test along these lines: >>> >>> bla0 >>> CHECK:bla1 >>> >>> will actually pass, because the CHECK pattern is also part of the input >>> so it will readily match itself. You want the CHECK lines not to match >>> themselves, which you can easily do by introducing {{}} into the (middle >>> of the) pattern....

Hello every one! I''m making a project to a discipline in the university and the project is make a Linux router that grants QoS to Multimedia connections (the prof. say we can use Open Source Soft. :) or reinvent the wheel). I have been googeling and googeling and i found the l7-filter in source forge and the spectacular simple language that is TCNG. Well the problem is how can i

...ipt type="text/javascript" src="prototype.js"></script> </head> <body> <form action="bllalba"> <table> <tr> <td>Input1</td> <td><input id="input1" type="text" name="bla1" /></td> <td>Input2</td> <td><input id="input2" class="focusable" type="text" name="bla2" /></ td> </tr> </table> <script type="text/javascript"> $(''input1''...

...gion.find(:all, :conditions => [ "parent_id = ?", @region.parent.id],:order=>"id") end The problem is that it doesn''t even display the onChange javascript code: <select id="region_id" name="region[id]"><option value="2">bla1</option> <option value="3">bla2</option> <option value="4">bla3</option></select><br> <select id="region_id" name="region[id]"> <option value="61" selected="selected">blop1</option&g...

...t; > > While doing so, if any file in src or dest location has a xattr value which is more than 32 bytes long, rsync segfaults. > > root at ph3dev [ ~ ]# getfattr -d -m '' -- /opt/x > getfattr: Removing leading '/' from absolute path names > # file: opt/x > user.bla1="1234567890abcdef1234567890abcdef1" --------> 33 bytes long > > After examining the coredump file, this happens at; > > rsync/xattrs.c > Line 277 in 2f9b963 > > sum_init(xattr_sum_nni, checksum_seed); > > Here md5 is used by default and md5 usage is prohibite...

Hello list, I suspect this is more a linux question than an R question, but I'll describe my situation in case anyone here knows of an elegant solution. I'm using Sweave and R to create thousands of customized reports. Within an R loop, I have R create a table.tex file using the CAT function which, for each iteration, creates a unique table.tex file in a subdirectory of the directory

Hi, From looking at the puppetd --help, there is not currently (at 0.22.4) a method of specifying tags in the puppetd.conf. I was hoping to use this for the following reason: Currently, I use ''noop = true'' in my puppetd.conf, and run ''puppetd --no-noop {tags}'' to install the configurations that I am happy with. This is because I''m currently

...-arXHpvxog <src> <dest> While doing so, if any file in src or dest location has a xattr value which is more than 32 bytes long, rsync segfaults. root at ph3dev [ ~ ]# getfattr -d -m '' -- /opt/x getfattr: Removing leading '/' from absolute path names # file: opt/x user.bla1="1234567890abcdef1234567890abcdef1" --------> 33 bytes long After examining the coredump file, this happens at; rsync/xattrs.c Line 277 in 2f9b963 sum_init(xattr_sum_nni, checksum_seed); Here md5 is used by default and md5 usage is prohibited in fips mode. Is there any way to work...

...thoncode', 'print "hi"') C=elwms('run_python', 'A',A, 'B',B, 'pythoncode', pythoncode) D=elwms('run_python', 'A',A+1, 'B',B*2, 'pythoncode', pythoncode) pythoncode=sprintf('import numpy\nresults=(A, B, [ "bla1", "bla2" ])\n'); X=elwms('run_python', 'A',A, 'B',B, 'pythoncode', pythoncode) print(A) print(B) print(C) print(D) print(X) This would pass around matrices A and B do some processing and return results. So you could use your old octave/matlab scr...

I need to apply three resources one immediatelly after another. It''s a ifdown/ifup commands, and command to generate /etc/network/interfaces file. I need to do ifdown, then rebuild interfaces, then ifup. I try to add simple relationship, but in this case some File resources are trying to be applied between ifdown and ifup. So they can''t connect to Puppet master to verify

Currently I''m trying to figure out the best zfs layout for a thumper wrt. to read AND write performance. I did some simple mkfile 512G tests and found out, that per average ~ 500 MB/s seems to be the maximum on can reach (tried initial default setup, all 46 HDDs as R0, etc.). According to http://www.amd.com/us-en/assets/content_type/DownloadableAssets/ArchitectureWP_062806.pdf I would