search for: sharedspace

...nk to this bot on llvm.org >> once it >> graduates from the Experimental pane on greendragon. > > Thank you! Polly is now available, but individual sites are not > accessible: > > http://lab.llvm.org:8080/coverage/coverage-reports/clang/coverage/Users/buildslave/jenkins/sharedspace/clang-stage2-coverage-R at 2/llvm/tools/polly/lib/Transform/FlattenSchedule.cpp.html > > I get: Forbidden > > You don't have permission to access > /coverage/coverage-reports/clang/coverage/Users/buildslave/jenkins/sharedspace/clang-stage2-coverage-R at 2/llvm/tools/polly/lib/T...

I've configured the bot to test lld and polly. The first batch of reports for the new tools are not ready yet, but anyone can monitor the build: http://lab.llvm.org:8080/green/view/Experimental/job/clang-stage2-coverage-R/ Matthias, I will ask around about adding a link to this bot on llvm.org once it graduates from the Experimental pane on greendragon. thanks, vedant > On Sep 23,

On 01/12/2016 10:26 PM, Kostya Serebryany wrote: > Hi Tobias, > > What machine is that? > We have seen this and similar tests be flaky on older Linux kernels due > to kernel bug(s). > May I ask you to run the same test (just built with clang) on the same > machine for ~100000 times and see if it ever crashes? > > clang++

These ran to completion without error. :( > On Jan 12, 2016, at 3:23 PM, Chris Matthews <chris.matthews at apple.com> wrote: > > I’m running this on green-dragon-03 which is running OSX 10.10.5. > > /Users/buildslave/jenkins/sharedspace/clang-stage1-cmake-RA_workspace\@2/clang-build/bin/clang++ ../llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread > while true; do for((i=0;i<10;i++)); do ./a.out || echo ===============FAILED================ & done ; wait; done > > Seems like it is getting about 225 runs...

...n can vary widely depending on the value of -DLLVM_TARGETS_TO_BUILD. Enabling coverage shouldn't increase the name section size much. I only see one place where this happens, and it's relatively cold: http://lab.llvm.org:8080/coverage/coverage-reports/llvm/coverage/Users/buildslave/jenkins/sharedspace/clang-stage2-coverage-R at 2/llvm/lib/Transforms/Instrumentation/InstrProfiling.cpp.html#L512 <http://lab.llvm.org:8080/coverage/coverage-reports/llvm/coverage/Users/buildslave/jenkins/sharedspace/clang-stage2-coverage-R at 2/llvm/lib/Transforms/Instrumentation/InstrProfiling.cpp.html#L512>...

...letion without error. :( > >> On Jan 12, 2016, at 3:23 PM, Chris Matthews <chris.matthews at apple.com <mailto:chris.matthews at apple.com>> wrote: >> >> I’m running this on green-dragon-03 which is running OSX 10.10.5. >> >> /Users/buildslave/jenkins/sharedspace/clang-stage1-cmake-RA_workspace\@2/clang-build/bin/clang++ ../llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread >> while true; do for((i=0;i<10;i++)); do ./a.out || echo ===============FAILED================ & done ; wait; done >> >> Seems like it is getting ab...

I see that the following test fails if reverse iteration of SmallPtrSet is enabled: /clang/test/SemaCXX/warn-loop-analysis.cpp/ This is because in SemaStmt.cpp we iterate SmallPtrSet and output warnings about the variables not used in the loop. Expected output: /warning: variables 'i', 'j', and 'k' used in loop condition not modified/ Output with reverse iteration:

...: > >> These ran to completion without error. :( >> >> On Jan 12, 2016, at 3:23 PM, Chris Matthews <chris.matthews at apple.com> >> wrote: >> >> I’m running this on green-dragon-03 which is running OSX 10.10.5. >> >> /Users/buildslave/jenkins/sharedspace/clang-stage1-cmake-RA_workspace\@2/clang-build/bin/clang++ >> ../llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread >> while true; do for((i=0;i<10;i++)); do ./a.out || echo >> ===============FAILED================ & done ; wait; done >> >> Seems like...

I had an old build of llc with FE instrumentation, the name section size is about 5MB. Using coverage is likely to cause the name section to be larger as there are more references to dead/unused function names. What do you see when readelf --string-dump=__llvm_prf_names llc David On Tue, Jun 27, 2017 at 2:23 PM, Xinliang David Li <davidxl at google.com> wrote: > > > On Tue,

It is expected and not unusual to need to update the lit test in such case. I'd need to see exactly which test breaks and how to know though. Best, -- Mehdi 2017-09-18 13:17 GMT-07:00 Johan Engelen <jbc.engelen at gmail.com>: > The fix (https://reviews.llvm.org/D37961) does not work. From what I > have learned thusfar, the module identifier is used as filename sometimes >

...2, 2016, at 3:23 PM, Chris Matthews <chris.matthews at apple.com <mailto:chris.matthews at apple.com>> wrote: >>>>> >>>>> I’m running this on green-dragon-03 which is running OSX 10.10.5. >>>>> >>>>> /Users/buildslave/jenkins/sharedspace/clang-stage1-cmake-RA_workspace\@2/clang-build/bin/clang++ ../llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread >>>>> while true; do for((i=0;i<10;i++)); do ./a.out || echo ===============FAILED================ & done ; wait; done >>>>> >>>...

...PM, Chris Matthews <chris.matthews at apple.com <mailto:chris.matthews at apple.com>> wrote: >>>>>> >>>>>> I’m running this on green-dragon-03 which is running OSX 10.10.5. >>>>>> >>>>>> /Users/buildslave/jenkins/sharedspace/clang-stage1-cmake-RA_workspace\@2/clang-build/bin/clang++ ../llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread >>>>>> while true; do for((i=0;i<10;i++)); do ./a.out || echo ===============FAILED================ & done ; wait; done >>>>>> >...