Segmentation Fault : Optimizing for the common case

Team members: RongrongZhong (Leader), TivadarPapai (Explosives), KonstantinosMenychtas(Assassin)

Segmentation Fault Manifesto

A spectre is haunting compiler optimizations -- the spectre of Segmentation Fault. All the compiler optimization teams have entered a competition to exorcise this spectre.

It is high time that Segmantion Fault should openly, in the face of the whole world, publish their optimizations, their aims, their tendencies, and meet this nursery tale of the spectre of seg-faulting with a modest manifestation :

  • We intend to optimize for the common case (which programmer has not seg-faulted ? What is more common than that spectre ?)
  • We intend to optimize for speed (what kind of optimization do you expect to have your program finish faster than a seg-fault?)
  • Through irony, self-sarcasm, modesty and true hacking, we shall prevail.

Calendar

  • Meeting 24th March : 17.00 Name, Manifesto, Wiki setup
  • Meeting 25th March : 15.30 Rongrong introduces her source
  • Meeting 26th March : 15.30 Constant propagation discussion (data structures)

TODO

  • Global Constant Propagation
  • Delete those control flow statements with empty bodies
  • Merge the output calls
  • Compare with the gimple tree of original Gcc outputs and find other useful optimizations
Edit | Attach | Watch | Print version | History: r17 | r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r7 - 2008-03-26 - RongrongZhong
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding URCS? Send feedback