[LLVMdev] Scheduler Roadmap

dag at cray.com dag at cray.com
Mon Jul 9 08:33:41 PDT 2012


Hal Finkel <hfinkel at anl.gov> writes:

> On Fri, 11 May 2012 10:26:41 -0500
> <dag at cray.com> wrote:
>
>> Hal Finkel <hfinkel at anl.gov> writes:
>> 
>> >> Actually, we don't have any problem releasing tests.  We have done
>> >> so before when sending patches.  The problem is the people we got
>> >> the tests from.  Some are from proprietary test suites, others are
>> >> from sensitive codes, etc.  It's often not up to us at all.
>> >
>> > I completely understand. Why don't we start by having you prepare
>> > LLVM IR files, and associated outputs, for x86_64 from your
>> > frontends only from open-source codes. As a first step, you could
>> > even just generate LLVM IR files for us from the codes in the LLVM
>> > test suite. We could setup a buildbot based on those files (which I
>> > believe would be easy to do), and then we can actively test trunk
>> > LLVM against those files.
>> 
>> I like this idea.  It'll work for C/C++ but not Fortran.  Since there
>> is no Fortran ABI one has to link with our Fortran compiler &
>> libraries to get an executable that actually works.
>> 
>> But let me think about this some more.  I would really like to expand
>> the LLVM testbase if we can.  It will be a long process since I'll
>> have to get all these tests approved for release.  I can't give a
>> timeline on that at all.  I think it will be a very gradual process.
>
> Out of curiosity, what is your current thinking on this?

I would still like to do it.  I haven't had any conversations with
management yet, however.  It will take some time to get everything in
order.

                               -Dave



More information about the llvm-dev mailing list