similar to: RFC: Add bitcode tests to test-suite

Some perhaps relevant aspects that make testing users of LLVM like Halide challenging: Halide uses the LLVM C++ APIs, but there isn't a good way to lock-step update it. So if we were to directly test Halide, it wouldn't link against the new LLVM. Practically speaking though, the LLVM IR generated by Halide should continue to work with newer LLVM optimizations and code generation. So the

>I think the real question is: Is this the best way to have a kind of 'halide buildbot' that can inform the LLVM developer community? Halide already has a buildbot running every few hours which is being used to inform LLVM developer community when something breaks. It would be a lot more useful however to have the tests in an LLVM repository to inform LLVM devs which test broke right

On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > Hi Chandler, et al., > > While this proposal to put IR into the test suite technically non-problematic, I've convinced myself that this is a suboptimal direction for the LLVM project. Here's what I think would be better: > > - We create a test-suite/Frontends directory, and open this directory to actively-maintained

On Thu, Feb 18, 2016 at 10:03 AM, Mehdi Amini via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Feb 18, 2016, at 8:42 AM, Philip Reames via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > >> Hi Chandler, et al., > >> > >> While this proposal to put IR into the

On 02/18/2016 09:08 AM, David Blaikie wrote: > > > On Thu, Feb 18, 2016 at 8:42 AM, Philip Reames via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > > > On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > > Hi Chandler, et al., > > While this proposal to put IR into the test suite

On Thu, Feb 18, 2016 at 10:03 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Feb 18, 2016, at 8:42 AM, Philip Reames via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > >> Hi Chandler, et al., > >> > >> While this proposal to put IR into the test suite

The bot failure can be reproduced with: ./bin/llvm-config "--ldflags" "--libs" "--system-libs" all-targets analysis asmparser asmprinter bitreader bitwriter codegen core debuginfodwarf executionengine instrumentation interpreter ipo irreader linker mc mcjit objcarcopts option profiledata scalaropts support target Looking... -- Mehdi > On Feb 12, 2016, at

Sent from my iPhone > On Feb 29, 2016, at 3:39 PM, Alina Sbirlea <alina.sbirlea at gmail.com> wrote: > > > >> On Mon, Feb 29, 2016 at 2:06 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >>> On Feb 29, 2016, at 1:50 PM, Alina Sbirlea <alina.sbirlea at gmail.com> wrote: >>> >>> >>> >>> On Mon, Feb

----- Original Message ----- > From: "Mehdi Amini via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Alina Sbirlea" <alina.sbirlea at gmail.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Monday, February 29, 2016 7:06:51 PM > Subject: Re: [llvm-dev] RFC: Add bitcode tests to test-suite > Sent from my iPhone > On Feb

Looks like this problem is also affecting the Go bindings build. http://lab.llvm.org:8011/builders/clang-x86_64-debian-fast/builds/34538/steps/test/logs/stdio Peter On Fri, Feb 12, 2016 at 10:20:50AM -0800, Ahmed Bougacha via llvm-dev wrote: > +Quentin > > > -Ahmed > > On Fri, Feb 12, 2016 at 10:16 AM, Alina Sbirlea via llvm-dev < > llvm-dev at lists.llvm.org>

> On Feb 29, 2016, at 10:50 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > > > From: "Mehdi Amini via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Alina Sbirlea" <alina.sbirlea at gmail.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Monday, February 29, 2016 7:06:51 PM > Subject: Re: [llvm-dev] RFC:

I really don't understand this. Why is a C++ reference useful? Instead, we have an IR reference: the unoptimized IR. I think it pretty important to not phrase everything in terms of C or C++ or Clang... =/ What if there are IR constructs that simply cannot be produced by C++? We're adding lots of those for managed languages. If there is a practical concern with having IR-based test

> On Feb 29, 2016, at 11:28 PM, Chandler Carruth <chandlerc at google.com> wrote: > > I really don't understand this. Why is a C++ reference useful? Instead, we have an IR reference: the unoptimized IR. Mmmmm, thinking more about it, yes we could compile the IR two times and use the unoptimized one as a reference. However, right now the tests are only running llc, so the

On Mon, Feb 29, 2016 at 2:06 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Feb 29, 2016, at 1:50 PM, Alina Sbirlea <alina.sbirlea at gmail.com> > wrote: > > > > On Mon, Feb 29, 2016 at 12:18 PM, Mehdi Amini <mehdi.amini at apple.com> > wrote: > >> >> On Feb 29, 2016, at 11:40 AM, Mehdi Amini via llvm-dev < >> llvm-dev at

> On Feb 29, 2016, at 1:50 PM, Alina Sbirlea <alina.sbirlea at gmail.com> wrote: > > > > On Mon, Feb 29, 2016 at 12:18 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote: > >> On Feb 29, 2016, at 11:40 AM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:

All, To get the discussion going in a focused manner, here is an initial patch with a running test. The test is from the Halide suite and is checking the correctness of several simd operations. (Notes: the patch is large due to the number of operations being tested; I expect a lot of changes before actually landing it, this is simply to continue the discussion using a concrete example.)

> On Feb 29, 2016, at 11:16 AM, Alina Sbirlea via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > All, > > To get the discussion going in a focused manner, here is an initial patch with a running test. The test is from the Halide suite and is checking the correctness of several simd operations. > (Notes: the patch is large due to the number of operations being tested;

> On Feb 29, 2016, at 11:40 AM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> >> On Feb 29, 2016, at 11:16 AM, Alina Sbirlea via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> All, >> >> To get the discussion going in a focused manner, here is an initial patch with a running

On Mon, Feb 29, 2016 at 12:18 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Feb 29, 2016, at 11:40 AM, Mehdi Amini via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > On Feb 29, 2016, at 11:16 AM, Alina Sbirlea via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > All, > > To get the discussion going in a focused manner, here

On 18/02/2016 19:12, Alina Sbirlea via llvm-dev wrote: > > > I have more questions for Alina. What kind of tests do you have: > > - "the compiler takes the bitcode and generates code without crashing" > - "the compiled test runs without crashing" > - "the compiled test will produce an output that be checked > against a