search for: dllvm_reverse_iteration

...: >> >> FYI, I just successfully performed a 3-stage bootstrap with >> stage2/stage3 object file comparison on x86_64-apple-darwin16 for >> llvm/clang/clang-tools-extra/compiler-rt/libcxx/openmp/polly using our >> custom fink packaging scripts with the >> -DLLVM_REVERSE_ITERATION:BOOL=ON cmake option. There were no >> stage2/stage3 object file comparison failures or test suite >> regressions. >> I do have one question though. Is there any particular reason >> not to leave this option on for deployed release builds of the >> compiler? &gt...

FYI, I just successfully performed a 3-stage bootstrap with stage2/stage3 object file comparison on x86_64-apple-darwin16 for llvm/clang/clang-tools-extra/compiler-rt/libcxx/openmp/polly using our custom fink packaging scripts with the -DLLVM_REVERSE_ITERATION:BOOL=ON cmake option. There were no stage2/stage3 object file comparison failures or test suite regressions. I do have one question though. Is there any particular reason not to leave this option on for deployed release builds of the compiler? Other than possibly running into some extreme co...

...troduced "reverse iteration" of unordered containers (currently only enabled for SmallPtrSet). I would now like to take this effort forward and propose to do the following: 1. We are in the process of setting up an internal nightly buildbot which would build llvm with the cmake flag -DLLVM_REVERSE_ITERATION:BOOL=ON. This will make all supported containers iterate in reverse order by default. We would then run "ninja check-all". Any failing unit test is a sign of a potential non-determinism. 2. With the toolchain built by the above buildbot we also want to run LNT tests and our entire int...

...rrently only enabled for > > SmallPtrSet). > > I would now like to take this effort forward and propose to do the > > following: > > > > 1. We are in the process of setting up an internal nightly buildbot > > which would build llvm with the cmake flag - > > DLLVM_REVERSE_ITERATION:BOOL=ON. > > This will make all supported containers iterate in reverse order by > > I hope you mean all supported *unordered* containers here. :-) > > > default. We would then run "ninja check-all". Any failing unit test is a > > sign of a potential non-determi...

...>>> > I would now like to take this effort forward and propose to do the >>> > following: >>> > >>> > 1. We are in the process of setting up an internal nightly buildbot >>> > which would build llvm with the cmake flag - >>> > DLLVM_REVERSE_ITERATION:BOOL=ON. >>> > This will make all supported containers iterate in reverse order by >>> >>> I hope you mean all supported *unordered* containers here. :-) >>> >>> > default. We would then run "ninja check-all". Any failing unit test is &gt...

Thanks everyone! What are the best tools/techniques to expose such non-deterministic behavior? My hope is to reproduce it on a smaller test (e.g. use some sanitizer and thus make the compiler *fail* when building the test) - Currently these failures only tell me “there is some bug in your code” without any hints where to look for it. Michael > On Apr 18, 2018, at 9:18 PM, Steven Wu

> On Apr 18, 2018, at 9:11 AM, Roman Lebedev via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Wed, Apr 18, 2018 at 5:45 PM, Michael Zolotukhin via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> Recently I committed a change (r330175) that passed all my testing, but >> failed on several bots. Namely, these are the failed ones: