similar to: LLVM coverage report

Hi, I'd like to announce a new code coverage bot: http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html The purpose of the bot is to make high-quality coverage reports available to llvm developers, and to provide additional testing for clang's code coverage implementation. The coverage data clang generates allows the reporting tool to render execution counts for code

Hi, Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) Thanks, Mehdi

> On May 19, 2016, at 8:59 AM, Sylvestre Ledru <sylvestre at debian.org> wrote: > > Le 16/05/2016 à 19:19, Mehdi Amini a écrit : >> Hi, >> >> Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) > This is now fixed: http://llvm.org/reports/coverage/ > I skimmed the results, and it seems that there

Hi Chris, llvm.org/perf gives again error 500s. I remember you had a look the last time. Would you mind looking again? Also, is there something which we could do to make LNT more robust. Do you have an idea what the last issue was about? Thanks, Tobias -------- Original Message -------- Subject: buildbot failure in LLVM on polly-perf-O3-polly-scev-codegen-isl Date: Fri, 21 Feb 2014 17:08:44

> On May 16, 2016, at 11:58 AM, Sylvestre Ledru <sylvestre at debian.org> wrote: > > Le 16/05/2016 à 19:19, Mehdi Amini a écrit : >> Hi, >> >> Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) > I am in charge of this. I had some recent issues with cmake but I think > I fixed them today. >

The next LLVM social in Paris will happen on June 14th, 2017. Everyone interested in LLVM, Clang, lldb, Polly, lld, ... is invited to join. Event details, including registration (free but mandatory) at http://www.meetup.com/LLVM-Clang-social This edition will be particularly busy (and interesting !) as we are delighted to welcome 3 guest speakers: - Hal Finkel (Argonne National Laboratory)

> Polly fails on mips, s390x & powerpc (plenty of errors + a timeout: > http://paste.debian.net/343829/ ) Are the mips failures regressions? I haven't started building/testing polly yet so I don't know the current state of mips support for it. > -----Original Message----- > From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of > Sylvestre Ledru via

On the 25. September, the next LLVM social will take place in Paris. Everyone interested in LLVM, clang, Polly, ... is invited to join. This is a casual meeting to get to know people working on LLVM or interested to learn about LLVM. There is no fixed schedule. We just meet to get to know each other and to discuss. No previous knowledge about LLVM is required. We will meet at IRILL, where we

On Sun, Mar 22, 2020 at 9:05 PM Andrew Kelley <andrew at ziglang.org> wrote: > > On 3/19/20 9:51 AM, Hans Wennborg via llvm-dev wrote: > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > > release branch at 35627038123. > > > > Source code and docs are available at > > https://prereleases.llvm.org/10.0.0/#rc5 and > >

Umesh Kalappa <umesh.kalappa0 at gmail.com> writes: > Hi Justin , > > Thank you for the confirmation and we would like to know that ,going > forward the clang has the support the gcc gcov format or use the > -fprofile-instr-generate -fcoverage-mapping and get ride of gcov > format . Going forward, the -fprofile-instr-generate -fcoverage-mapping (which I'll refer to as

Hi Justin , Thank you for the confirmation and we would like to know that ,going forward the clang has the support the gcc gcov format or use the -fprofile-instr-generate -fcoverage-mapping and get ride of gcov format . We are planing to customize the clang code coverage for embedded world ,before we start tweaking the gcov / -fprofile-instr-generate code-base ,we would like to take feedback

On Feb 12, 2014, at 11:43 PM, Kostya Serebryany <kcc at google.com> wrote: > > > > On Thu, Feb 13, 2014 at 11:10 AM, Bob Wilson <bob.wilson at apple.com> wrote: > > On Feb 12, 2014, at 10:31 AM, Kostya Serebryany <kcc at google.com> wrote: > >> Hi, >> >> Justin is making nice commits for llvm-cov, so I thought we may continue this

Hi, Alan Thanks for making it clear. But I was more confused now :( I tested on a simple program and used both gcov and lcov to get branch coverage. The code and build commands as below: *Example simple.cc* #include <string> // If not comment this line, the branch coverage won't reach to 100% // #include <iostream> int main(int argc, const char* argv[]) { std::string str =

Hi, llvm/clang experts I need to get the branch coverage for some testing code. But i found gcov can't give a expected coverage which may count some 'hidden branch' in (See stackoverflow answer <https://stackoverflow.com/questions/42003783/lcov-gcov-branch-coverage-with-c-producing-branches-all-over-the-place>). Instead, I turn to use clang and the 'source-based code

Hi, Alan Really very excited to receive your email and sorry to be slow replying, it has been exceptionally busy over the last few days ;( Your explanation made the problem clear to me. So gcov branch coverage should be called condition coverage and clang region coverage is branch coverage in fact(also known as *decision/C1*), right? And llvm/clang will support all the following coverage

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 Monday, June 23rd, the next LLVM social will take place in Paris. Everyone interested in LLVM, clang, Polly, ... is invited to join. !! This time again at IRILL !! This is a casual meeting to get to know people working on LLVM or interested to learn about LLVM. There is no fixed schedule. We just meet to get to know each other and to discuss. No previous knowledge about LLVM is required. We

On Feb 12, 2014, at 10:31 AM, Kostya Serebryany <kcc at google.com> wrote: > Hi, > > Justin is making nice commits for llvm-cov, so I thought we may continue this discussion now. > The quick-and-dirty implementation of coverage (in asan) is getting some early users and they seem to be happy. > AsanCoverage allows to collect per-function or per-basic-block coverage

The bot hiccupped earlier but looks stable now. The average turnaround seems to be 3.5 hours. clang: http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html lld: http://lab.llvm.org:8080/coverage/coverage-reports/lld/index.html polly: http://lab.llvm.org:8080/coverage/coverage-reports/polly/index.html > On Sep 23, 2016, at 11:58 PM, Tobias Grosser via llvm-dev

2012/2/12 Tobias Grosser <tobias at grosser.es>: > On 02/08/2012 08:08 PM, Marcello Maggioni wrote: >> >> Hi, I'm using Polly to analyze memory access patterns for an >> university project and I'm trying to get polly working on some loops >> that polly marks as "containing non affine branches" . > > > Hi Marcello, > > sorry for the