[llvm-dev] Your help needed: List of LLVM Open Projects 2017
Vassil Vassilev via llvm-dev
llvm-dev at lists.llvm.org
Mon Feb 6 11:07:17 PST 2017
Thanks a lot for the project. Could you put it in the google doc
below? I'd appreciate if you could follow more-or-less the format. Are
you going to be the mentor.
On 06/02/17 19:29, Matthias Braun wrote:
> Here's another one:
> = Improve code generation testing =
> After instruction selection LLVM uses the MI (Machine Instruction)
> representation for programs. We recently added support for reading and
> writing this representation to disk
> (http://llvm.org/docs/MIRLangRef.html). Usage of this format for
> writing tests is growing and so is the desire to improve the format,
> tools and workflow. Improvements would be welcome:
> - Create a single consistent format instead of the current mix of yaml
> + IR + MIR
> - Do not print unnecessary information (we often print default values
> where the reader could deduce them)
> - Allow the representation to deduce successors of a basic block in
> common cases
> - Allow symbolic names instead of just numbers for virtual registers
> - Helper passes: Strip IR information, rename blocks and values, debug
> information, ...
> - Create a bugpoint mode (or a new tool) to reduce .mir test cases
> - Write recommendations and guides for .mir based tests
> - Matthias
>> On Jan 16, 2017, at 5:18 AM, Vassil Vassilev via llvm-dev
>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>> Hi folks,
>> Happy new year!
>> Last LLVM Developers' Meeting I had a BoF: 'Raising Next Generation
>> LLVM Developers'. It was suggested that we should update our open
>> projects page and possibly restructure it a little bit.
>> I volunteered to do this work and I need your help.
>> Chandler and I started working on a google doc . We pinged few
>> code owners asking them to list of work items we should get done in
>> 2017 but we do not have the manpower. Now we would like to ask for
>> your input, too.
>> I believe an up to date list can serve as a good entry point for
>> students, interns and new contributors.
>> Feel free to propose a new item or comment under an existing one. I
>> expect to start gradually updating the page beginning of Feb.
>> -- Vassil
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev