The LLVM Compiler Infrastructure
Site Map:
Download!
Download now: LLVM 2.5

Try the
online demo

View the open-source
license

Search this Site


Status Updates
Developer Mtgs
Useful Links
Maintained by:
Chris Lattner
LLVM Developers' Meeting
  1. Important Notes
  2. Agenda
  3. Attendees
  • What: The second general meeting of LLVM Developers and Users.
  • Why: To get acquainted, learn how LLVM is used, and exchange ideas.
  • When: August 1, 2008
  • Where: Apple Campus (4 Infinite Loop, Cupertino, CA)

We are in the early stages of planning the second LLVM group meeting. At this point in time, we are asking that anyone interested in attending email the answers to these questions to the person organizing this meeting:

  • Are you willing to give a talk? on what topic?
  • What topics are your primary interests?
  • Are you or your company willing to make a donation?

The meeting is tentatively scheduled between 8:00 AM and 5:00 PM Pacific Time. The schedule of talks has not yet been decided. If you are interested in speaking, please let us know what topic you'd like to present.

This table lists all attendees that have expressed interest in attending this year's conference.

Unconfirmed Attendees
NameOrganization
Owen AndersonApple, Inc.
Daniel BerlinGoogle
Chandler Carruth
Evan ChengApple, Inc.
Eric ChristopherApple, Inc.
Samuel Crow
Daniel Dunbar
Ryan GovostesAlacatia Labs, Inc.
Kurt HarrimanGreenplum
Robert HundtGoogle
Dale JohannesenApple, Inc.
Jonathan JohnsonAlacatia Labs, Inc.
Ted KremenekApple, Inc.
Chris LattnerApple, Inc.
Nick LewyckyGoogle
Bruno Cardoso Lopes
Nuno Lopes
Harry Metcalfe
Scott Michel
Steve NaroffApple, Inc.
Ted Neward
Devang PatelApple, Inc.
Joseph RanieriAlacatia Labs, Inc.
Chuck RoseAdobe Systems Incorporated
Tim Sander
Robert StaudingerUniversity of Salzburg, Austria
Joe StroutInspiring Applications, Inc.
Mike StumpApple, Inc.
Bill WendlingApple, Inc.
Robert Zeh
Chuck (Chengyan) ZhaoUniversity of Toronto

Total unconfirmed: 31

If your name is misspelled, or organization affiliation isn't correct, please email us, and we'll correct it.