OMR Architecture Meetings

[0xdaryl]

All Eclipse OMR contributors are invited to participate in a recurring call to discuss technical topics relating to the Eclipse OMR architecture. These calls will be of interest to anyone interested in OMR technology and helping to shape its evolution. Each call will have a set agenda from topics proposed in advance by contributors.

Date	Agenda/ Minutes	Replay	Main Topics
July 4, 2024	Agenda		Open for proposed topics
June 20, 2024	Agenda	Replay	JitBuilder 2.0 update
Feb 1, 2024	Agenda	Replay	OMR release proposal
Nov 23, 2023	Agenda	Replay	Scalar bit compress and expand opcodes; API const correctness; JIT atomic symbols; JitBuilder 2.0
Aug 31, 2023	Agenda	Replay	JitBuilder 2.0 Extension code walkthrough
Aug 17, 2023	Agenda	Replay	JitBuilder 2.0 Continued
July 20, 2023	Agenda	Replay	JitBuilder 2.0
Apr 27, 2023	Agenda	Replay	Vector IL opcodes proposal; arraycmplen IL opcode proposal
Jan 26, 2023	Agenda	Replay	OMR 2022 Retrospective and 2023 goals
Nov 3, 2022	Agenda	Replay	Compiler API unit testing
Oct 20, 2022	Agenda	Replay	JitBuilder 2.0 update and OMR integration
Sept 22, 2022	Agenda	Replay	Masked vector IL opcodes
Aug 4, 2022	Agenda	Replay	JIT scratch memory profiling
June 23, 2022	Agenda	Replay	New PR build features and launch triggers
May 26, 2022	Agenda	Replay	l2a IL opcode semantics
Apr 14, 2022	Agenda	Replay	JitBuilder 2.0 update; Add build flags to PR testing
Mar 31, 2022	Agenda	Replay	cgroup v2 support
Mar 3, 2022	Agenda	Replay	CI pipeline tools; Linux core dump code
Feb 17, 2022	Agenda	Replay	Compiler memory leak discussion
Feb 3, 2022	Agenda	Replay	2021 retrospective; 2022 plans
Nov 25, 2021	Agenda	Replay	Vector IL redesign
Aug 5, 2021	Agenda	Replay	JitBuilder 2.0
July 22, 2021	Agenda	Replay	GC Parallelism and Adaptive Threading
June 10, 2021	Agenda	Replay	Compiler address formatting; compiler backend refactoring
May 13, 2021	Agenda	Replay	Opcode evaluator decision; Prune vector IL opcodes
Apr 29, 2021	Agenda	Replay	Revisit: Clean up centralized opcode enums
Apr 15, 2021	Agenda	Replay	Extensible class visibility and extension modifiers; Eliminating unused IL OpCodes; Python DevOps dependency; Eliminating signed commit requirement
Mar 18, 2021	Agenda	Replay	Discussion on defining the compiler API
Mar 4, 2021	Agenda	Replay	Linkage properties refactoring; CI trigger
Feb 18, 2021	Agenda	Replay	Port library initialization; discuss compiler Options processing status
Feb 4, 2021	Agenda	Replay	Misc. code cleanup tasks; size-optimized build option
Jan 21, 2021	Agenda	Replay	2020 retrospective; 2021+ plans
Dec 3, 2020	Agenda	Replay	RISC-V CI builds, opcode enum refactoring
Nov 5, 2020	Agenda	Replay	Load/store sequences on Power; migrate CI builds from Travis CI
Oct 22, 2020	Agenda	Replay	Port library initialization with JitBuilder and OMR compiler
Sept 24, 2020	Agenda	Replay	Power instruction fusion, ObjectFormat for call encoding
Sept 10, 2020	Agenda	Replay	New IL opcodes sbyteswap and lbyteswap
Aug 27, 2020	Agenda	Replay	Contributing BenefitInliner; JitBuilder2 update
July 16, 2020	Agenda	Replay	Add Dynamic Breadth First Scan Ordering to GC
June 18, 2020	Agenda	Replay	OMR compiler extensibility study; stale issue review
June 4, 2020	Agenda	Replay	OMR integration into Julia; stale issue review
May 7, 2020	Agenda	Replay	Improve new Jenkins pipeline; misc CI improvements
Apr 23, 2020	Agenda	Replay	Azure CI pipelines; GitHub actions
Apr 9, 2020	Agenda	Replay	IL Tree Interpreter; fomrobjptr_t; Binary Encoding Testing; JitBuilder 2.0 Repo
Mar 12, 2020	Agenda	Replay	JitBuilder 2.0 Proposal
Feb 27, 2020	Agenda	Replay	Re-architect Compiler Memory Infrastructure Follow-up
Feb 13, 2020	Agenda	N/A	Re-architect Compiler Memory Infrastructure
Jan 30, 2020	Agenda	Replay	OMR GC technology roadmap
Jan 16, 2020	Agenda	Replay	Port OpenJ9 shared classes implementation to OMR
Dec 12, 2019	Agenda	Replay	OMR component testing ideas and plans for 2020
Dec 5, 2019	Agenda	Replay	OMR architecture roadmap and priorities; OWL project
Nov 21, 2019	Agenda	Replay	Source code formatting with Clang; ILOpCode table definition
Nov 14, 2019	Agenda	Replay	Localized compiler target environment
Oct 24, 2019	Agenda	Replay	OMR releases
Oct 10, 2019	Agenda	Replay	OMR default components; OMR API documentation; OS macro usage
Sept 26, 2019	Agenda	Replay	OMR release 0.1.0; compiler arch directory renaming; ternary family IL opcode rename; remove imulover IL opcode
Sept 12, 2019	Agenda	Replay	Contributing LLJB to OMR
June 20, 2019	Agenda	Replay	Formalizing IL semantics; TR::newvalue IL opcode
June 6, 2019	Agenda	Replay	Switching inliners from the command line
May 23, 2019	Agenda	Replay	Concurrent scavenge read barrier patching
May 9, 2019	Agenda	Replay	TR::intrinsic IL opcode draft
Apr 25, 2019	Agenda	Replay	InstructionDelegate
Mar 28, 2019	Agenda	Replay	Progress on Options re-design
Feb 25, 2019	Agenda	Replay	Dr. Nadi's update on design for extensibility
Feb 21, 2019	Agenda	Replay	Improved inlining for OMR
Jan 17, 2019	Agenda	Replay	Low-level memory allocator class simplification
Dec 19, 2018	Agenda	Replay	CodeGen simplification phase
Dec 12, 2018	Agenda	Replay	IL opcode issue template, compare opcode API, TR namespace usage
Nov 21, 2018	Agenda	Replay	Tril roadmap and wishlist
Oct 24, 2018	Agenda	Replay	Opcode guidelines, rename "NonHelpers"
Sept 12, 2018	Agenda	Replay	Proposed write barrier IL opcodes
Aug 15, 2018	Agenda	Replay	Re-architect Options processing
Aug. 1, 2018	Agenda	Replay	Read barrier and FMA IL opcodes
July 18, 2018	Agenda	Replay	Fate of C++ STL in compiler
July 11, 2018	Agenda	Replay	Default floating point semantics
June 20, 2018	Agenda	Replay	Out-of-line instruction common design
June 6, 2018	Agenda	Replay	Extensible class revirtualization proposal
May 23, 2018	Agenda	Replay	TR IL specification
Apr 27, 2018	Agenda	Replay	OMR initialization
Apr 12, 2018	Agenda	Replay	Revamping vector IL opcodes
Mar 28, 2018	Agenda	Replay	JitBuilder status & focus 2018
Feb 28, 2018	Agenda	N/A	Intro, 2018 focus, TR::Node transmutation

Details

• Bi-weekly on Thursdays @ 2:00 pm EST (GMT -5). The duration is only the time required to cover the agenda topics, not exceeding 90 minutes.
• Calls will use Webex (audio only, no video) with screen sharing. They will be recorded and published to the Eclipse OMR YouTube channel for reference and for those who could not participate live.
• Agenda and minutes from each meeting will be represented using GitHub issues. If necessary, questions and discussion on the topics raised during those meetings can continue in the corresponding issue after the meeting has concluded. All past and future agendas and minutes will be linked from this GitHub issue for easy reference.
• Agenda topics for an upcoming meeting must be proposed no later than one week prior to the meeting so that there is ample time to communicate the agenda to the community. Topics are proposed through comments on the appropriate meeting agenda issue. The moderator will finalize the agenda and communicate with the Eclipse OMR community via the #general channel on the OMR Slack workspace.
• Transcript-like minutes won't be taken, but summaries of key decisions and actions will be published to the minutes issue when appropriate.
• Access details will be included in the agenda communicated prior to each meeting.

[charliegracie]

@0xdaryl would it be possible to move the Compiler Architecture meetings into Google docs instead of creating a separate issue for each meeting. This Issue is ok as a central location but I think having an Issue for each individual meetings seems like a waste of Issues.

[0xdaryl]

@charliegracie: My thinking behind using GH issues rather than some external medium was to try and centralize where we keep information for this project and keep it as close to the repo as possible. Adding yet another place to search for information with different access controls wasn't appealing to me. Eclipse OMR contributors all have GH accounts and its easy for anyone to add comments or questions, tag other project members (which often elicits an email prompting their attention), and be tracked back to the project (or at the very least GH) if we're using Issues. My intention was to allow those who couldn't participate in the meetings directly, or those who had questions or comments afterwards, to add comments in the Issue agenda to further the discussion if necessary. I wasn't convinced GoogleDocs or any other non-GH medium offered a significant value-add over that.

I don't feel that at most 26 issues/year is a burden. We have a rich set of labels to tag all Issues in Eclipse OMR and it's very easy to filter and search for what you're looking for if you're concerned about pollution.