Programming project I: Unsafe Thread-specific Points-to Analysis
Posted February 6, 2006; due March 8, 2006 at midnight

• Feb 21, 2006: The DTD definition of the output for the project is now available. A sample output can be viewed in your browser; to view this correctly, make sure that you put this file in the directory in which you are displaying the output.

  You will use the online handin program available from:
  https://handin.rutgers.edu/handin/jsp/login.jsp
  to turn in your project. Make sure to select the proper category and then login using your Rutgers DCS system logon and password. Remember to prepare a gzipped tar file of all the files necessary to run your project (but not the untouched SOOT files).

• Feb 20, 2006: Futher notes on Project I will be discussed in class tonight.
• Feb 17, 2006: A simple threaded program on which to test your analyses. The jar file should be included in your classpath and cs516.test.Simulation is the main class.
• Look at the Lhotak & Hendren CC'03 paper for pseudo-code of a points-to analysis worklist algorithm.

Programming project II: Safe Thread-specific Points-to Analysis
posted March 9, 2006; due April 24, 2006 at midnight

• April 5, 2006: Standard data for Muffin to use for one of your runs to gather metrics in project 2.

• April 3, 2006: Notes on how to run the benchmarks.

• March 27, 2006: Bruno's slides on *J are now available.

  Additional files to show how to use *J can be found here:

  • Main.java,
  • ThreadCallGraphPrinter.java,
  • Dynamic Call Graph

• March 26, 2006: For documentation on *J we will provide skeleton files about how to call it. Also, you can look at a sample log of how to run a simple program analysis and/or consult with Bruno Dufour's master's thesis on *J, especially the chapter describing the *J Framework.

Last updated by Barbara Ryder at 4:11pm on April 5, 2006.