search for: abtest

...emoved, excepting any backend passes required to run. Pete Sent from my iPhone On Mar 25, 2016, at 5:29 PM, Matthias Braun via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Ok I cleaned it up and added some explaining comments. It's in llvm/utils/abtest now. - Mathias On Mar 25, 2016, at 4:40 PM, Michael Gottesman <mgottesman at apple.com<mailto:mgottesman at apple.com>> wrote: On Mar 25, 2016, at 4:37 PM, Matthias Braun <matze at braunis.de<mailto:matze at braunis.de>> wrote: And as we are on the topic of bisecting/di...

Ok I cleaned it up and added some explaining comments. It's in llvm/utils/abtest now. - Mathias > On Mar 25, 2016, at 4:40 PM, Michael Gottesman <mgottesman at apple.com> wrote: > > >> On Mar 25, 2016, at 4:37 PM, Matthias Braun <matze at braunis.de <mailto:matze at braunis.de>> wrote: >> >> And as we are on the topic of bisecti...

...es when a pass is added/removed, excepting any backend passes required to run. Pete Sent from my iPhone > On Mar 25, 2016, at 5:29 PM, Matthias Braun via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Ok I cleaned it up and added some explaining comments. It's in llvm/utils/abtest now. > > - Mathias > >>> On Mar 25, 2016, at 4:40 PM, Michael Gottesman <mgottesman at apple.com> wrote: >>> >>> >>> On Mar 25, 2016, at 4:37 PM, Matthias Braun <matze at braunis.de> wrote: >>> >>> And as we are on the...

...emoved, excepting any backend passes required to run. Pete Sent from my iPhone On Mar 25, 2016, at 5:29 PM, Matthias Braun via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Ok I cleaned it up and added some explaining comments. It's in llvm/utils/abtest now. - Mathias On Mar 25, 2016, at 4:40 PM, Michael Gottesman <mgottesman at apple.com<mailto:mgottesman at apple.com>> wrote: On Mar 25, 2016, at 4:37 PM, Matthias Braun <matze at braunis.de<mailto:matze at braunis.de>> wrote: And as we are on the topic of bisecting/di...

...f scripts are useful (I have written the same script 3-4 times). Why not clean it up and commit it under utils, maybe creating a debug utility directory and stick it with bisect? (Just a random thought). I would love not to have to write it again ; ). Michael > > - Matthias > > <abtest.py> > >> On Mar 25, 2016, at 4:05 PM, Michael Gottesman via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> I will describe the complete process for completeness thus hopefully forestalling all questions [tell me if I did...

.../cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160325/00a4a071/attachment-0002.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: abtest.py Type: text/x-python-script Size: 5901 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160325/00a4a071/attachment-0001.bin> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/att...

I will describe the complete process for completeness thus hopefully forestalling all questions [tell me if I did not ; )]. There is not much to it TBH. ./utils/bisect is a dumb python script that allows for arbitrary bisecting via the exit status of a script it runs . The way you use it is you write a script (lets call it test.sh). Then you invoke: ./utils/bisect --start=N --end=M ./test.sh

> In the swift-world we use utils/bisect + a single number all the time + extra verifications. It works really well. Can you describe to me what you mean by that exactly? Are you using the single number in the LLVM back end or somewhere else? From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Michael Gottesman via llvm-dev Sent: Friday, March 25, 2016 12:35 PM To: