Date: Fri, 19 May 2006 02:37:32 +0300 From: Rostislav Krasny <rosti.bsd@gmail.com> To: Colin Percival <cperciva@freebsd.org> Cc: is@rambler-co.ru, davidxu@freebsd.org, freebsd-current@freebsd.org Subject: Re: FreeBSD-SA-06:14.fpu Message-ID: <20060519023732.ea4221dd.rosti.bsd@gmail.com> In-Reply-To: <44554601.5090105@freebsd.org> References: <20060430142408.fcd60069.rosti.bsd@gmail.com> <44554601.5090105@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Apr 2006 16:19:29 -0700 Colin Percival <cperciva@freebsd.org> wrote: > Rostislav Krasny wrote: > > Other possible solution is making the fpu_clean_state() optional by > > something like following: > > > > #ifdef BUG_FXSAVE > > #define fpu_clean_state() __fpu_clean_state() > > #else > > #define fpu_clean_state() ; > > #endif > > > > ... and including "options BUG_FXSAVE" to GENERIC. > > Yes, this is probably the right solution. My priority was to fix the > bug; optimizing performance comes second. Ok. Is this solution going to be done some day? I could try to make a patch but I'm not familiar with the build infrastructure internals. P.S. what is a better option name: "options BUG_FXSAVE" or "options AMD_FXSAVE"?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060519023732.ea4221dd.rosti.bsd>