similar to: Is anyone experienced writing Sphinx documentation?

+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 > ... >

Seems pretty useful! +1 to Jon's comments. Procedural remark: patches normally go to llvm-commits not llvm-dev. --paulr > -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > Jonathan Roelofs via llvm-dev > Sent: Wednesday, December 14, 2016 8:09 AM > To: Tom de Vries; llvm-dev at lists.llvm.org; James Y Knight > Subject: Re:

See: http://llvm.org/docs/CommandGuide/FileCheck.html It is not required to pipe output to FileCheck; there is the --input-file option, which allows you to run FileCheck on an existing disk file. Something like this: FileCheck %s --input-file a.rpt --check-prefix=A FileCheck %s --input-file b.rpt --check-prefix=B FileCheck %s --input-file c.rpt --check-prefix=C If there are common parts to each

"--strict-whitespace By default, FileCheck canonicalizes input horizontal whitespace (spaces and tabs) which causes it to ignore these differences (a space will match a tab). The/--strict-whitespace/ <http://llvm.org/docs/CommandGuide/FileCheck.html#cmdoption--strict-whitespace>argument disables this behavior. End-of-line sequences are canonicalized to UNIX-style ‘n’ in all

http://llvm.org/docs/CommandGuide/FileCheck.html says FileCheck ignores white spaces/tabs by default unless you use "--strict-whitespace" option. 2013/3/15 Shawn <shaolin.xie at ia.ac.cn>: > Hi all: > I'm writing testcase for the MC layer regression in llvm, the > disassembled string is a bit complicate, for example: > "IALU.T0 (I0) = BIU0.DM ; REPEAT

Hi, TL;DR - We should update the bot(s) responsible for building the LLVM documentation so that they use recommonmark 0.5.0, and apply https://reviews.llvm.org/D63211. Full context: I recently started trying to build the sphinx docs. However, a change by Jordan (r363100) resulted in me no longer being able to build them, even though the build bots were green and he could build them himself.

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

If you look at the FileCheck documentation page: http://llvm.org/docs/CommandGuide/FileCheck.html you'll find this intriguing example of combining -DAG with -NOT (slightly amended to avoid some potential confusion): ; CHECK-DAG: BEFORE ; CHECK-NOT: BETWEEN ; CHECK-DAG: AFTER The page says this will reject the sequence "AFTER BEFORE", which is correct. It's intuitively obvious

Hello, FileCheck allows us to define match variables and use them on subsequent lines. This is quite useful, but could be even more useful if it was possible to use the variable later on the same line it matched. For example, I would want to write this: ; CHECK: bic [[REG:r[0-9]+]], [[REG]], #3 But I currently can't because [[REG]] will only match a REG variable defined on a _previous_

Michael Kruse via llvm-dev <llvm-dev at lists.llvm.org> writes: > Am Mo., 6. Juli 2020 um 08:55 Uhr schrieb David Greene <david.greene at hpe.com>: >> Is the behavior of CHECK-SAME documented anywhere? It's not on the main >> FileCheck web page. I assumed it started over from the beginning of the >> line but now I'm not sure. > >

Hi all: I'm writing testcase for the MC layer regression in llvm, the disassembled string is a bit complicate, for example: "IALU.T0 (I0) = BIU0.DM ; REPEAT AT ( 2 ) ;;" The spaces in the disassembled string is error-prone. Is there any option to tell the FileCheck utility to ignore the spaces ? Kind Regards. Shawn.

Nope. Sorry, your expectation is incorrect. "BETWEEN BEFORE AFTER" would be accepted, because: (1) the first –DAG matches BEFORE; (2) the –NOT range starts at the preceding match-point, i.e. the (end of the) BEFORE, thus does not find BETWEEN; (3) the second –DAG starts at the same point as the –NOT. That is, the first –DAG and the following –NOT *are* ordered; the –NOT and the

Hello I have pass operating on bitcode file which produces more than one equivalent representation. opt --my-pass <%s | Filecheck %s --my-pass generates files a.rpt b.rpt c.rpt . How do i write test without writing all 3 files to stdin. I have considered CHECK-LABEL for each. it creates bulky checks. Thanks Mahesh -------------- next part -------------- An HTML attachment was

On 05/24/2018 08:46 AM, via llvm-dev wrote: > Background > ---------- > > FileCheck [0] is a cornerstone testing tool for the LLVM project. It > has grown new features over the years to meet new needs, but these > sometimes have surprising and counter-intuitive behavior [1]. This > has become even more evident in Joel Denny's recent quest to repair > what seemed like

Michael Kruse via llvm-dev <llvm-dev at lists.llvm.org> writes: >> Would this not work? >> >> CHECK-SAME: ![[ACCESS_GROUP_INNER:[0-9]+]] >> CHECK-SAME: ![[ACCESS_GROUP_OUTER:[0-9]+]] >> >> I don't think CHECK-SAME is sensitive to order within the line. This >> works for me in my metadata tests but maybe I've just been lucky. > > AFAIU

Background ---------- FileCheck [0] is a cornerstone testing tool for the LLVM project. It has grown new features over the years to meet new needs, but these sometimes have surprising and counter-intuitive behavior [1]. This has become even more evident in Joel Denny's recent quest to repair what seemed like an obvious defect [2] but which led me to the conclusion [3] that FileCheck sorely

On Jan 17, 2013, at 9:57 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Thu, Jan 17, 2013 at 7:51 PM, Sean Silva <silvas at purdue.edu> wrote: >> On Thu, Jan 17, 2013 at 8:36 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >>> We have to options: >>> (a) replace 'FileCheck' with '%FileCheck' in all tests, and teach

On Thu, Jan 17, 2013 at 10:20 AM, Jim Grosbach <grosbach at apple.com> wrote: > > On Jan 17, 2013, at 9:57 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > >> On Thu, Jan 17, 2013 at 7:51 PM, Sean Silva <silvas at purdue.edu> wrote: >>> On Thu, Jan 17, 2013 at 8:36 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >>>> We have to

On Jan 17, 2013, at 10:30 AM, Eli Bendersky <eliben at google.com> wrote: > On Thu, Jan 17, 2013 at 10:20 AM, Jim Grosbach <grosbach at apple.com> wrote: >> >> On Jan 17, 2013, at 9:57 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >> >>> On Thu, Jan 17, 2013 at 7:51 PM, Sean Silva <silvas at purdue.edu> wrote: >>>> On Thu,

On 13 December 2016 at 17:45, Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Over a month ago I submitted some patches to begin documenting PDB file > format. These files are in llvm/docs/PDB. When I view the docs online > though, they appear stale. Many of the pages are blank, containing only a > file header. This matches up with my initial commit of the