Tamarin:WeeklyUpdates: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Update dial-in info)
Line 4: Line 4:
* 2:00pm Pacific Time (21:00 UTC) on Tuesdays
* 2:00pm Pacific Time (21:00 UTC) on Tuesdays
** (5PM Eastern US, 11PM Oslo, 6AM (Wed) Seoul, 7AM (Wed) Melbourne)
** (5PM Eastern US, 11PM Oslo, 6AM (Wed) Seoul, 7AM (Wed) Melbourne)
* Meeting ID: 8262746 (TAMARIN)
 
** California: 408-536-9900
* Location: Tel: 866 705 2554 (us), 913 227 1201 (int’l), Passcode:
** Toll-Free(US & Canada): 877-220-5439
914008
** International: +1-408-536-9900
* Duration: 60 minutes
* Duration: 60 minutes
* join irc.mozilla.org #tamarin for attendence taking and questions
* join irc.mozilla.org #tamarin for attendence taking and questions

Revision as of 19:36, 26 February 2008

These updates concern Tamarin and related projects only.

Meeting Details

  • 2:00pm Pacific Time (21:00 UTC) on Tuesdays
    • (5PM Eastern US, 11PM Oslo, 6AM (Wed) Seoul, 7AM (Wed) Melbourne)
  • Location: Tel: 866 705 2554 (us), 913 227 1201 (int’l), Passcode:

914008

  • Duration: 60 minutes
  • join irc.mozilla.org #tamarin for attendence taking and questions

Tamarin Tech Summit, February 1, 2008

15th January 2008

Attendees

  • Erik
  • Moh
  • Jason
  • Marsha
  • Brent
  • Benjamin
  • Ed
  • Rick
  • Steven
  • Jeff
  • Seo

Announcements

  • Tamarin summit February 1st at Adobe – SF

Updates

Jason (ActionMonkey)

  • Land ActionMonkey changes to mozilla-central.
  • Incremental marking
  • Thread safe
  • Performance number
  • tracking bug:
  • mozilla-central is the trunk in hg

Steven

  • TT now building on linux

Moh (Vtune)

  • jit profiling api
  • step 1
    • account: premier account,
    • request: "JIT profiling API of VTUNE"
    • contact: Gary Carleton
  • step 2 - shipped with vtune
  • step 3 - talk about open source

Marsha (Instrumentation)

  • posted a patch for changes needed to invoke Vtune from TC
  • an update is coming


Summit Topics

  • Vtune profiling
  • Code walkthrough of the JIT - what optimizations are applied (or not applied)


Older meetings