Date: Thu, 14 Nov 2002 11:40:58 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Doug Rabson <dfr@nlsystems.com> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/ia64/gen _setjmp.S Message-ID: <20021114194057.GA856@dhcp01.pn.xcllnt.net> In-Reply-To: <1037298535.19149.8.camel@builder02.qubesoft.com> References: <200211140640.gAE6eNq9016231@repoman.freebsd.org> <200211141009.45000.dfr@nlsystems.com> <20021114181340.GA603@dhcp01.pn.xcllnt.net> <1037298535.19149.8.camel@builder02.qubesoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 14, 2002 at 06:28:55PM +0000, Doug Rabson wrote: > > > > Why do you need a flushrs in longjmp() anyway? > > All you really need to achieve is that ar.bsp equals ar.bspstore > > before you set ar.bspstore, right? > > (note that the loadrs is missing a cover or an alloc) > > You would need a flushrs if you really wanted to use longjmp for thread > switching, otherwise you would lose the stacked registers of the thread > you were switching away from. But you need a setjmp to save that context, right? How would you otherwise return to the thread? > > It's good to eventually optimize setjmp/longjmp for the common case, > > but at this time it's all we have and I think we'd better focus on > > being functionally complete. > > I don't think thread switching is (should be) part of the functional > specification of setjmp/longjmp. I don't disagree, but deischen's swapcontext stuff is not here yet and not having libc_r is hurting now. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021114194057.GA856>