Skip to content
  1. Jun 07, 2004
    • Reid Spencer's avatar
      Commit For New Tool: llvm-abcd (Analysis of ByteCode Dumper). This tool · db5c86d0
      Reid Spencer authored
      will (eventually) provide statistical analysis of bytecode files as well
      as the ability to dump them in a low level format (slot numbers not
      resolved). The purpose of this is to aid in the Type!=Value change of
      bug 122. With this initial release, llvm-abcd merely dumps out the
      bytecode. However, the infrastructure for separating bytecode parsing from
      handling the parsing events is in place. The style chosen is similar to
      SAX XML parsing where a handler object is called to handlign the parsing
      events. This probably isn't useful to anyone but me right now as there is
      no analysis yet, and the dumper doesn't work on every bytecode file. It
      will probably be useful by the end of this week. Note that there is some
      duplication of code from the bytecode reader.  This was done to eliminate
      errors from being introduced in the reader and to minimize the impact to
      other LLVM developers. At some point, the Analyzer and the Reader will be
      integrated to use the same infrastructure. Also, sorry for the minor change
      to Instruction.h but I just couldn't bring myself to write code that
      depends on Instruction internals.
      
      llvm-svn: 14048
      db5c86d0
  2. Jun 02, 2004
  3. Jan 05, 2004
  4. Oct 28, 2003
  5. Oct 21, 2003
  6. Oct 16, 2003
  7. Sep 16, 2003
  8. Sep 15, 2003
  9. Sep 13, 2003
  10. Aug 28, 2003
  11. May 14, 2003
  12. Dec 24, 2002
  13. Dec 06, 2002
  14. Nov 20, 2002
  15. Oct 30, 2002
  16. Sep 18, 2002
  17. Aug 01, 2002
  18. May 22, 2002
  19. Mar 06, 2002
  20. Oct 31, 2001
  21. Oct 13, 2001
  22. Sep 15, 2001
  23. Sep 14, 2001
    • Chris Lattner's avatar
      This checkin represents some cleanup of the backend, implementing the following things: · 0a823a06
      Chris Lattner authored
      1. The TargetMachine structure is free to decide the process a particular target uses to generate code.
      2. All of the gooee details of the sparc backend are now localized in the lib/CodeGen/TargetMAchine/Sparc directory.  The Sparc.h file that is globally visible is just a stub.
      3. The Sparc.h file that esxists now will dissapear entirely someday when we have multiple backends chosen by a factory of some sort.
      
      llvm-svn: 559
      0a823a06
  24. Sep 07, 2001
  25. Aug 23, 2001
  26. Jul 26, 2001
  27. Jul 21, 2001
  28. Jul 03, 2001
  29. Jun 06, 2001
Loading