If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Add new component for JavaScript JIT compilers

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Administration
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jandem, Assigned: dkl)

Tracking

Production

Details

We'd like to add a new component to the Core product. Default assignee, QA contact and other fields not mentioned below should be the same as for the JavaScript Engine component.

Details:

* Name: JavaScript Engine: JIT
* Product: Core
* Description: JavaScript engine's JIT compilers

The "JavaScript Engine:" prefix is there for consistency with other subcomponents.

FWIW, the idea for a new component was proposed in the following mailing list thread: https://lists.mozilla.org/pipermail/dev-tech-js-engine-internals/2013-October/001230.html
A few of us in Brussels were (independently, it seems!) discussing this sort of thing.  We think there shouldn't just be a new component for the JIT -- we really should have several different JS components.  The list we came up with (assuming I remember it fully) was:

* GC
* JIT
* Front end
* Standard library
* "VM" (representation structures, interpreter, etc.)
* "General" (all existing bugs, unless someone feels like retriaging them; also all new bugs, for people who aren't sure of a better spot)

Also, while Core :: JavaScript Engine: GC is not entirely unreasonable, it does make filing slightly harder.  I would much prefer a top-level product for JS, with subcomponents for those others.  If that can't be done because of Bugzilla flag suckage, oh well.  (But, given the number of things that use the sub-colon scheme, maybe in that case we should push on the BMO people to fix Bugzilla in this regard.)
For this bug, let's just add a JIT component, and let's talk the rest over on IRC or js-engine, preferably after the summit.
(Assignee)

Comment 3

4 years ago
Done
Assignee: nobody → dkl
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.