search for: rl313631

...> >     string > >      > on the first line of the test file: "NOTE: Assertions have > been > >      > autogenerated by utils/update_llc_test_checks.py"... > >      > and both of these do as of: > https://reviews.llvm.org/rL313631 <https://reviews.llvm.org/rL313631> > >     <https://reviews.llvm.org/rL313631 > <https://reviews.llvm.org/rL313631>> > >      > <https://reviews.llvm.org/rL313631 > <https://reviews.llvm.org/rL313631> > >     <https://...

...to-generated assertions (look for this > > string > > > on the first line of the test file: "NOTE: Assertions have been > > > autogenerated by utils/update_llc_test_checks.py"... > > > and both of these do as of: https://reviews.llvm.org/rL313631 > > <https://reviews.llvm.org/rL313631> > > > <https://reviews.llvm.org/rL313631 > > <https://reviews.llvm.org/rL313631>> ), then it's easy to observe > the > > > diffs by re-running that script after your code patch is applie...

...e test files have auto-generated assertions (look for this > string > > on the first line of the test file: "NOTE: Assertions have been > > autogenerated by utils/update_llc_test_checks.py"... > > and both of these do as of: https://reviews.llvm.org/rL313631 > <https://reviews.llvm.org/rL313631> > > <https://reviews.llvm.org/rL313631 > <https://reviews.llvm.org/rL313631>> ), then it's easy to observe the > > diffs by re-running that script after your code patch is applied: > > $ /path...

...gt; > > > If the test files have auto-generated assertions (look for this string > > on the first line of the test file: "NOTE: Assertions have been > > autogenerated by utils/update_llc_test_checks.py"... > > and both of these do as of: https://reviews.llvm.org/rL313631 > > <https://reviews.llvm.org/rL313631> ), then it's easy to observe the > > diffs by re-running that script after your code patch is applied: > > $ /path/to/update_llc_test_checks.py --llc=/path/to/local/and/new/llc > > lea-3.ll > > $ svn diff lea-3.ll >...

...the patch at D37896. > > If the test files have auto-generated assertions (look for this string > on the first line of the test file: "NOTE: Assertions have been > autogenerated by utils/update_llc_test_checks.py"... > and both of these do as of: https://reviews.llvm.org/rL313631 > <https://reviews.llvm.org/rL313631> ), then it's easy to observe the > diffs by re-running that script after your code patch is applied: > $ /path/to/update_llc_test_checks.py --llc=/path/to/local/and/new/llc > lea-3.ll > $ svn diff lea-3.ll As described by Sanjay in...

...s in an updated version of the patch at D37896. If the test files have auto-generated assertions (look for this string on the first line of the test file: "NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py"... and both of these do as of: https://reviews.llvm.org/rL313631 ), then it's easy to observe the diffs by re-running that script after your code patch is applied: $ /path/to/update_llc_test_checks.py --llc=/path/to/local/and/new/llc lea-3.ll $ svn diff lea-3.ll On Tue, Sep 19, 2017 at 5:23 AM, Haidl, Michael via llvm-dev < llvm-dev at lists.llvm.org>...

...s in an updated version of the patch at D37896. If the test files have auto-generated assertions (look for this string on the first line of the test file: "NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py"... and both of these do as of: https://reviews.llvm.org/rL313631 ), then it's easy to observe the diffs by re-running that script after your code patch is applied: $ /path/to/update_llc_test_checks.py --llc=/path/to/local/and/new/llc lea-3.ll $ svn diff lea-3.ll On Tue, Sep 19, 2017 at 5:23 AM, Haidl, Michael via llvm-dev <llvm-dev at lists.llvm.org<m...

I am currently improving the D37896 to include the suggestions from Chad. However, running the lit checks for the x86 backend I observe some changes in the generated MC, e.g.: llvm/test/CodeGen/X86/lea-3.ll:13:10: error: expected string not found in input ; CHECK: leal ([[A0]],[[A0]],2), %eax ^ <stdin>:10:2: note: scanning from here orq %rdi, %rax ^ <stdin>:10:2:

This conversation has (partially) moved on to D37896 now, but if possible I was hoping that we could perform this in DAGCombiner and remove the various target specific combines that we still have. At least ARM/AARCH64 and X86 have cases that can hopefully be generalised and removed, but there will probably be a few legality/perf issues that will occur. Simon. > On 14 Sep 2017, at 06:23,