Date: Sun, 7 Aug 2011 11:19:07 -0400 From: Super Bisquit <superbisquit@gmail.com> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: freebsd-ppc@freebsd.org Subject: Re: Lags and setjmp Message-ID: <CA%2BWntOvM7CT_HLG0VzujPAfkLsRJzKT6axXG2PmDpAbqSqTAEw@mail.gmail.com> In-Reply-To: <CA%2BWntOvwEP4E88RqruvVzUtNxMkmWZ8H0n=MpFqDZ6ySqPSBUA@mail.gmail.com> References: <CA%2BWntOvpqj0FSE%2BcYA2UqsefvhaxPhaaKdaz3DC%2BPyFe01iRDA@mail.gmail.com> <4E3D5FA6.80207@freebsd.org> <CA%2BWntOvwEP4E88RqruvVzUtNxMkmWZ8H0n=MpFqDZ6ySqPSBUA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/6/11, Super Bisquit <superbisquit@gmail.com> wrote: > On Sat, Aug 6, 2011 at 11:37 AM, Nathan Whitehorn > <nwhitehorn@freebsd.org>wrote: > >> On 08/05/11 10:47, Super Bisquit wrote: >> >>> The file /usr/src/sys/powerpc/powerpc/**setjmp.S has >>> >>> #ifdef __powerpc64__ >>> >>> at line nine. Maybe this is affecting the system because: >>> the lag seems to occur on Xorg/Xserver with the cursor having to be >>> moved >>> before there is a response. >>> I'm wondering if setting the vale to powerpc instead of powerpc64 would >>> stop >>> this action. >>> >>> >> It wouldn't for the reason Justin said, and this file only applies to the >> kernel besides. I've also never experienced this bug you're referring to. >> Is >> X using longjmp/setjmp() internally? One thing we do not do is >> save/restore >> FP registers for long jumps. It's not required by the spec, but Linux >> does >> do it. >> -Nathan >> >> ______________________________**_________________ >> freebsd-ppc@freebsd.org mailing list >> http://lists.freebsd.org/**mailman/listinfo/freebsd-ppc<http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>; >> To unsubscribe, send any mail to >> "freebsd-ppc-unsubscribe@**freebsd.org<freebsd-ppc-unsubscribe@freebsd.org> >> " >> > > How's it going? > > Anyway, I'm not sure. I'll restart X with a more verbose output and will > attach the file next reply. > I'm curious, what machines are you using for the 9.0 PowerPC ? > I did not find anything. This problem only occurs with the G4 systems. Unless someone else has the same equipment, it's just an "annoyance" bug for me.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BWntOvM7CT_HLG0VzujPAfkLsRJzKT6axXG2PmDpAbqSqTAEw>