From 7e0281fe2ef55bd1504b53b5ab30caa4f429eb21 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Fri, 28 May 2004 20:41:37 +0000 Subject: [PATCH] Add links to new-featuer and code-cleanup bugs git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@13884 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/OpenProjects.html | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/docs/OpenProjects.html b/docs/OpenProjects.html index 56dcea8602a..3a5eb10ef63 100644 --- a/docs/OpenProjects.html +++ b/docs/OpenProjects.html @@ -15,6 +15,7 @@
  • What is this?
  • Improving the current system
      +
    1. Implementing Code Cleanup bugs
    2. Port glibc to LLVM
    3. Compile programs with the LLVM Compiler
    4. Extend the LLVM intermediate representation
    5. @@ -23,6 +24,7 @@
    6. Adding new capabilities to LLVM
        +
      1. Implementing new feature PRs
      2. Pointer and Alias Analysis
      3. Profile Guided Optimization
      4. New Transformations and Analyses
      5. @@ -79,6 +81,22 @@ can use improvement...

        + + + +
        + +

        +The LLVM bug tracker occasionally +has "code-cleanup" bugs filed in it. Taking one of these and fixing it is a good +way to get your feet wet in the LLVM code and discover how some of its components +work. +

        + +
        +
        Port glibc to LLVM @@ -176,6 +194,18 @@ also be very rewarding.

        + + + + +
        + +

        Many ideas for feature requests are stored in LLVM bugzilla. Just search for bugs with a "new-feature" keyword.

        + +
        +