Opened 17 years ago
Last modified 3 years ago
#55 assigned enhancement
Clearing LispThread.currentThread()._values more efficiently
| Reported by: | ehuelsmann | Owned by: | ehuelsmann |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.9.3 |
| Component: | compiler | Version: | 1.2.0-dev |
| Keywords: | performance | Cc: | |
| Parent Tickets: |
Description
We currently clear _values all over the place; we could be more efficient some times.
Change History (26)
comment:1 by , 17 years ago
| Keywords: | performance added |
|---|
comment:2 by , 16 years ago
| Milestone: | → too-vague |
|---|
comment:3 by , 16 years ago
| Milestone: | too-vague → 1.0 |
|---|
comment:4 by , 16 years ago
Some work has been done in this department (on the unsafe-p-removal branch): specifically, all block types are now explicitly handled, while only TAGBODY was before - and incorrectly at that.
However, the main issue still stands.
comment:5 by , 16 years ago
One of the factors determining single-valued-ness of self-compiled functions is the %SINGLE-VALUED-P field in the compiland structure.
This field gets set to T during pass1 whenever any function call within that function returns T for the call to SINGLE-VALUED-P (which itself is located in pass2???).
comment:7 by , 15 years ago
| Milestone: | 1.0 → 1.1.0 |
|---|
comment:8 by , 14 years ago
| Milestone: | 1.1.0 → 1.2.0 |
|---|
comment:9 by , 13 years ago
| Priority: | major → blocker |
|---|---|
| Status: | new → assigned |
| Version: | → 1.2.0-dev |
Verify that the minimum api exists. Document it.
comment:10 by , 13 years ago
| Milestone: | 1.2.0 → 1.3.0 |
|---|
comment:13 by , 12 years ago
| Milestone: | 2.0.0 → 1.4.0 |
|---|
comment:18 by , 6 years ago
| Milestone: | 1.6.2 → 1.7.0 |
|---|
comment:23 by , 4 years ago
| Milestone: | 1.8.1 → 1.9.0 |
|---|
comment:24 by , 4 years ago
| Milestone: | 1.9.0 → 1.9.1 |
|---|
comment:25 by , 3 years ago
| Milestone: | 1.9.1 → 1.9.2 |
|---|
comment:26 by , 3 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
Note:
See TracTickets
for help on using tickets.
Operations like these:
(and possibly some others)
can be found enclosed in CLEAR-VALUES instructions, however, by nature, they can't be causing currentThread()._values to be set: only (lisp) function calls do that.