Tamarin:WeeklyUpdates: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Fix link to the tracing paper.)
No edit summary
 
(174 intermediate revisions by 20 users not shown)
Line 1: Line 1:
:''These updates concern Tamarin and related projects only.''
:''These updates concern Tamarin and related projects only.''


'''Meeting Details'''
'''Meeting Details (Changed as of 11/18/08)'''
* 2:00pm Pacific Time (21:00 UTC) on Tuesdays
* 10:00 AM Pacific Time (18:00 UTC) on Tuesdays
** (5PM Eastern US, 11PM Oslo, 6AM (Wed) Seoul, 7AM (Wed) Melbourne)
** 1PM Eastern US, 7PM Oslo, 3AM (Wed) Seoul, 5AM (Wed) Melbourne  
* Meeting ID: 8262746 (TAMARIN)
* Location: Tel: 877-220-5439 (US & Canada), +1-408-536-9900(International)
** California: 408-536-9900
** Meeting Place ID: 2000
** Toll-Free(US & Canada): 877-220-5439
* join irc.mozilla.org #tamarin for attendance taking and questions
** International: +1-408-536-9900
* Duration: 60 minutes
* join irc.mozilla.org #tamarin for attendence taking and questions




= 18th December 2007 =
'''Next meeting's Agenda Items (3/17/09):'''
* Canceled


== Attendees ==


* Marsha
* Brett
* Ed
* Steven
* Brendan
* Moh
* Benjamin
* Andreas Gal
* Dan Schaffer
* Jeff


== tamarin-tracing ==


* Adobe will push later today a branch of the code in tamarin-central (T-C), which introduces a trace-based just-in-time compiler.
= January 27, 2009 Meeting Notes =
* Research (http://www.ics.uci.edu/~franz/Site/pubs-pdf/ICS-TR-07-10.pdf) and experience with Tamarin indicate that tracing provides significant size and performance advantages over traditional static JIT compilers, especially when executing untyped JavaScript.
== Attendees ==
 
Jeff,  Steven, Brent, Tom, Dan Schaffer, Rick Reitmaier, Rob Winchell, Moh
* The new code will reside in a repository at:
== Agenda Topics ==
 
* Status Updates
  http://hg.mozilla.org/tamarin-tracing
 
* Tamarin-tracing (T-T) shares a common root with T-C and so the complete history of changes is recorded. Fixes from both branches will be merged to the other over time.
* T-T is currently optimized to run effectively on mobile devices. As such, its performance characteristics favor memory efficiency over speed.
* Not API compatible with T-C
* Calls to builtins can be optimized by rewriting builtins in interpreted (trace-able) byte code. This also leads to smaller object files
* The interpreter is and indirect threading Forth engine.
 
== Status ==
 
'''Mark H'''
* Q. How different are the APIs? A. Pretty different. They are not compatible, but the builts have already been ported, and you'll only need to port you own host objects.
 
* Shouldn't be too bad then.


* ChessApp working a bit better. JScript can call Tamarin and vice-versa. This allows workaround of missing event handling across engines since JScript event handlers can call Tamarin functions. Close to having Tamarin move chess pieces around the board.
== Meeting Discussion Notes ==
=== Status Updates ===


'''Benjamin'''
Jeff:
* Checked in a verifier refactoring. Some cleanup needed, but wanted to get it in.
* Put in a pipeline architecture where all code generators are driven off of api (similar to backend nanojit api)


* From earlier email:


Just a note: I'm working on a project to add valgrind memory annotations to
Steven
MMgc. This will allow valgrind to note improper use of GC memory.
* Spot bug fixing


The first step is quite simple: it will use the valgrind client requests
Dan Schaffer
described at
* Ecma 3 data acceptance tests
http://valgrind.org/docs/manual/mc-manual.html#mc-manual.clientreqs to
* If anyone sees any failures, send Dan Schaffer an email
declare freed memory as unaccessable.
* There may still be some lurking problems


The second step will be to check memory overruns (writes of multiple GC
Tom Harwood
allocations from a single call).
* Global optimizer stopped working on this for now
* Starting to work on verifier and code generators instead
* Jeff’s change broke GO code
* Tom filed a bug on that. Copy Jeff on that but.  


The third step will be a warning system for correct incremental marking. If
you write a pointer-like value to GC memory without using a write barrier,
it will warn. This has to be a conservative warning, of course.
I hope to have step I done by the first week of January.
- --BDS
'''Jason'''
* Stage 1 (ActionMonkey) just about complete. Waiting for reviews. "maybegc" api done. 4 or 5 patches ready to land.
* Stage 2, incremental GC, is next
'''Moh'''
* Profiled JSBench (http://gforge.ssllab.org/gf/project/jsbench/scmsvn/) from the UCI team. Shows one helper method (doubleToAtom) is responsible for ~46% of the time in one of the tests (Moldyn).
* Will study further to look for optimization opporunities


= Older meetings =
= Older meetings =
 
* [[Tamarin:WeeklyUpdates/2009-01-27|January 27, 2009]]
* [[Tamarin:WeeklyUpdates/2009-01-013|January 13, 2009]]
* [[Tamarin:WeeklyUpdates/2009-01-06|January 6, 2009]]
* [[Tamarin:WeeklyUpdates/2008-12-16|December 16, 2008]]
* [[Tamarin:WeeklyUpdates/2008-12-09|December 9, 2008]]
* [[Tamarin:WeeklyUpdates/2008-12-03|December 3, 2008]]
* [[Tamarin:WeeklyUpdates/2008-11-18|November 18, 2008]]
* [[Tamarin:WeeklyUpdates/2008-11-11|November 11, 2008]]
* [[Tamarin:WeeklyUpdates/2008-09-30|September 30, 2008]]
* [[Tamarin:WeeklyUpdates/2008-08-26|August 26, 2008]]
* [[Tamarin:WeeklyUpdates/2008-08-12|August 12, 2008]]
* [[Tamarin:WeeklyUpdates/2008-07-22|July 22, 2008]]
* [[Tamarin:WeeklyUpdates/2008-07-15|July 15, 2008]]
* [[Tamarin:WeeklyUpdates/2008-07-01|July 1, 2008]]
* [[Tamarin:WeeklyUpdates/2008-06-24|June 24, 2008]]
* [[Tamarin:WeeklyUpdates/2008-06-17|June 17, 2008]]
* [[Tamarin:WeeklyUpdates/2008-06-10|June 10, 2008]]
* [[Tamarin:WeeklyUpdates/2008-06-03|June 3, 2008]]
* [[Tamarin:WeeklyUpdates/2008-05-20|May 20, 2008]]
* [[Tamarin:WeeklyUpdates/2008-05-06|May 6, 2008]]
* [[Tamarin:WeeklyUpdates/2008-04-15|April 15, 2008]]
* [[Tamarin:WeeklyUpdates/2008-03-25|March 25, 2008]]
* [[Tamarin:WeeklyUpdates/2008-03-18|March 18, 2008]]
* [[Tamarin:WeeklyUpdates/2008-03-11|March 11, 2008]]
* [[Tamarin:WeeklyUpdates/TamarinSummit2008|Tamarin Tech Summit Agenda, February 1, 2008]]
* [[Tamarin:WeeklyUpdates/2008-01-15|January 15, 2008]]
* [[Tamarin:WeeklyUpdates/2008-01-08|January 08, 2008]]
* [[Tamarin:WeeklyUpdates/2007-12-18|December 18, 2007]]
* [[Tamarin:WeeklyUpdates/2007-12-01|December 11, 2007]]
* [[Tamarin:WeeklyUpdates/2007-12-01|December 11, 2007]]
* [[Tamarin:WeeklyUpdates/2007-12-04|December 4, 2007]]
* [[Tamarin:WeeklyUpdates/2007-12-04|December 4, 2007]]

Latest revision as of 00:52, 17 March 2009

These updates concern Tamarin and related projects only.

Meeting Details (Changed as of 11/18/08)

  • 10:00 AM Pacific Time (18:00 UTC) on Tuesdays
    • 1PM Eastern US, 7PM Oslo, 3AM (Wed) Seoul, 5AM (Wed) Melbourne
  • Location: Tel: 877-220-5439 (US & Canada), +1-408-536-9900(International)
    • Meeting Place ID: 2000
  • join irc.mozilla.org #tamarin for attendance taking and questions


Next meeting's Agenda Items (3/17/09):

  • Canceled



January 27, 2009 Meeting Notes

Attendees

Jeff, Steven, Brent, Tom, Dan Schaffer, Rick Reitmaier, Rob Winchell, Moh

Agenda Topics

  • Status Updates

Meeting Discussion Notes

Status Updates

Jeff:

  • Checked in a verifier refactoring. Some cleanup needed, but wanted to get it in.
  • Put in a pipeline architecture where all code generators are driven off of api (similar to backend nanojit api)


Steven

  • Spot bug fixing

Dan Schaffer

  • Ecma 3 data acceptance tests
  • If anyone sees any failures, send Dan Schaffer an email
  • There may still be some lurking problems

Tom Harwood

  • Global optimizer stopped working on this for now
  • Starting to work on verifier and code generators instead
  • Jeff’s change broke GO code
  • Tom filed a bug on that. Copy Jeff on that but.


Older meetings

Retrieved from "https://wiki.mozilla.org/index.php?title=Tamarin:WeeklyUpdates&oldid=134201"