search for: bar_addr

Displaying 4 results from an estimated 4 matches for "bar_addr".

2020 Jan 31
2
[RFC][FileCheck] New option to negate check patterns
...no-print-string | FileCheck %s --check-prefix=CHECK2 CHECK1<NAME>: mov [[REG:r[0-9]+]], #42 CHECK2-NOT: <NAME> It might work probably. We already have the ability to name parts of the output checked: // CHECK: Dynamic Relocations { // CHECK-NEXT: {{.*}} R_AARCH64_RELATIVE - [[BAR_ADDR:.*]] // CHECK: Symbols [ // CHECK-NEXT: Value: [[BAR_ADDR]] So adding a way for naming the whole line does not look an unreasonable/inconsistent extention to me I think. Best regards,​ George | Developer | Access Softek, Inc​​​​​​​ ________________________________ From: James Henderson...
2008 Aug 27
2
[LLVMdev] Mandatory duplicated incoming nodes on phis
...e an equivalent number of times. The attached code seems wrong, but it compiles as correct, and removing the duplicated incoming node causes an error. Is this expected? Cheers, Gary -- http://gbenson.net/ -------------- next part -------------- define internal i32 @func419(i32* %foo_addr, i32* %bar_addr, i32 %baz) { %method = load i32* %foo_addr br label %not_zero not_zero: switch i32 %baz, label %no_exception9 [ i32 6, label %bci_56 i32 7, label %bci_56 ] no_exception9: %bar = load i32* %bar_addr br label %bci_56 b...
2020 Feb 03
2
[RFC][FileCheck] New option to negate check patterns
...>: mov [[REG:r[0-9]+]], #42 > > CHECK2-NOT: <NAME> > > > > It might work probably. We already have the ability to name parts of > > the output checked: > > > > // CHECK: Dynamic Relocations { > > // CHECK-NEXT: {{.*}} R_AARCH64_RELATIVE - [[BAR_ADDR:.*]] > > > > // CHECK: Symbols [ > > // CHECK-NEXT: Value: [[BAR_ADDR]] > > > > So adding a way for naming the whole line does not look > > an unreasonable/inconsistent extention to me I think. > > > > Best regards,​ > > George | Develo...
2020 Jan 31
2
[RFC][FileCheck] New option to negate check patterns
Hi all, There have been a few cases recently where I've noticed two test cases in the same lit test that do the same thing except invert the CHECK, to show that something is NOT present. I'm talking about something like the following: # RUN: llvm-sometool --print-string | FileCheck %s --check-prefix=STRING # RUN: llvm-sometool --no-print-string | FileCheck %s --check-prefix=NO-STRING #