[llvm-dev] Uncovering non-determinism in LLVM - The Next Steps
Daniel Berlin via llvm-dev
llvm-dev at lists.llvm.org
Sun Jul 9 16:07:22 PDT 2017
On Sun, Jul 9, 2017 at 3:57 PM, Jack Howarth <
howarth.mailing.lists at gmail.com> wrote:
> On Sun, Jul 9, 2017 at 1:26 PM, Daniel Berlin <dberlin at dberlin.org> wrote:
> > On Sun, Jul 9, 2017 at 9:19 AM, Jack Howarth via llvm-dev
> > <llvm-dev at lists.llvm.org> wrote:
> >> 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?
> > Because it wouldn't accomplish anything.
> > The goal is to have a different iteration order than the default.
> > If you make this the default, that doesn't help, because now the default
> > reverse
> So perhaps I am doing this wrong? Should I have have the stage2 build
> -DLLVM_REVERSE_ITERATION:BOOL=ON and stage3 with that option
> so that any variation in the object files generated for the llvm build
> is picked up?
This would be ideal, yes :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev