search for: sedbak

...tax, so you need to run sed with the -E option. For example, when preparing the patch I created a file ( script.sed ) containing all of the lines that I copied into the commit message. Then, I ran this bash one-liner from the test directory: for f in $(find . -name '*.ll'); do sed -E -i ‘.sedbak' -f script.sed $f; done When I was happy with the results, then: find . -name ‘*.sedbak’ --exec rm -f {} \; Please let me know if that doesn’t work for you. -Daniel On Jan 23, 2018, at 8:33 PM, Alexandre Isoard via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.o...

...ith the -E > option. > > For example, when preparing the patch I created a file ( script.sed ) > containing all of the lines that I copied into the commit message. Then, I > ran this bash one-liner from the test directory: > for f in $(find . -name '*.ll'); do sed -E -i ‘.sedbak' -f script.sed $f; > done > > When I was happy with the results, then: find . -name ‘*.sedbak’ --exec > rm -f {} \; > > Please let me know if that doesn’t work for you. > > -Daniel > > On Jan 23, 2018, at 8:33 PM, Alexandre Isoard via llvm-dev < > llvm-dev...

...on. >> >> For example, when preparing the patch I created a file ( script.sed ) >> containing all of the lines that I copied into the commit message. Then, I >> ran this bash one-liner from the test directory: >> for f in $(find . -name '*.ll'); do sed -E -i ‘.sedbak' -f script.sed $f; >> done >> >> When I was happy with the results, then: find . -name ‘*.sedbak’ --exec >> rm -f {} \; >> >> Please let me know if that doesn’t work for you. >> >> -Daniel >> >> On Jan 23, 2018, at 8:33 PM, Alexandre...

...tax, so you need to run sed with the -E option. For example, when preparing the patch I created a file ( script.sed ) containing all of the lines that I copied into the commit message. Then, I ran this bash one-liner from the test directory: for f in $(find . -name '*.ll'); do sed -E -i ‘.sedbak' -f script.sed $f; done When I was happy with the results, then: find . -name ‘*.sedbak’ --exec rm -f {} \; Please let me know if that doesn’t work for you. -Daniel On Jan 23, 2018, at 8:33 PM, Alexandre Isoard via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.o...

...tax, so you need to run sed with the -E option. For example, when preparing the patch I created a file ( script.sed ) containing all of the lines that I copied into the commit message. Then, I ran this bash one-liner from the test directory: for f in $(find . -name '*.ll'); do sed -E -i ‘.sedbak' -f script.sed $f; done When I was happy with the results, then: find . -name ‘*.sedbak’ --exec rm -f {} \; Please let me know if that doesn’t work for you. -Daniel On Jan 23, 2018, at 8:33 PM, Alexandre Isoard via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.o...

Hello, Is there a script to update those test cases? I see mention of a sed script in the commit message but when I try it (see attached) on sed I get the following error: sed: file script line 2: invalid reference \3 on `s' command's RHS Did I lose something in a copy-paste? Is it not really a sed script? How do I run it? On Fri, Jan 19, 2018 at 9:15 AM, Daniel Neilson via