#1925: remove config step auto::jit
-----------------------+----------------------------------------------------
Reporter: coke | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: configure | Version: 2.11.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-----------------------+----------------------------------------------------
Changes (by jkeenan):
* type: => bug
* component: none => configure
* milestone: 2.11 =>
Comment:
IIRC, when we ripped out the old, dysfunctional JIT, we considered
removing this config step (and its associated tests as well). But some
people felt we'd be getting the new JIT before long, so there was no harm
in leaving it in.
Well, "before long" hasn't arrived yet, so I have no objection to
proceeding with removal.
But perhaps we could get a GCI task out of this:
'''Evaluate the impact of removing configuration step auto::jit'''.
Task would be to (a) identify the impact of removing any of the values
currently set by this configuration step -- hopefully demonstrating that
their removal does no harm; (b) actually remove the config step, its
tests, etc.
How does that sound?
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1925#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
