[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #860: C_in_stackp could be optimized (was: C_in_s
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #860: C_in_stackp could be optimized (was: C_in_stackp may be buggy) |
Date: |
Sun, 03 Jun 2012 16:21:53 -0000 |
#860: C_in_stackp could be optimized
-----------------------------+----------------------------------------------
Reporter: felix | Owner: felix
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: core libraries | Version: 4.7.x
Resolution: | Keywords: C_in_stackp nursery GC
-----------------------------+----------------------------------------------
Changes (by felix):
* priority: major => minor
* type: defect => enhancement
Comment:
I think this is actually ok. Inlining the in-stack test would definitely
be worthwhile, though, to reduce function call overhead during GC. (Joerg
Wittenberger suggested this as well on `chicken-hakcers`)
--
Ticket URL: <http://bugs.call-cc.org/ticket/860#comment:2>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Chicken-janitors] #860: C_in_stackp could be optimized (was: C_in_stackp may be buggy),
Chicken Trac <=