[CRIU] BUG: CRIU corrupt floating point state after checkpoint

Dmitry Safonov 0x7f454c46 at gmail.com
Wed Sep 25 04:54:26 MSK 2019


On 9/25/19 2:51 AM, Dmitry Safonov wrote:
> On 9/25/19 2:41 AM, Diyu Zhou wrote:
>> Sure. See:
>> https://github.com/vmexit/fpu-debug
>>
>> I'm very new to github, so let me know if there is any issue
>> accessing the link.
> 
> Ok, might this quick-fast oneliner help?
> 
> --->8---
> diff --git a/compel/src/main.c b/compel/src/main.c
> index 51bac099fe5e..ca3c0318093e 100644
> --- a/compel/src/main.c
> +++ b/compel/src/main.c
> @@ -41,7 +41,7 @@ typedef struct {
>  static const flags_t flags = {
>  #if defined CONFIG_X86_64
>         .arch           = "x86",
> -       .cflags         = COMPEL_CFLAGS_PIE,
> +       .cflags         = COMPEL_CFLAGS_PIE " -mfpmath=387",

Maybe the right one would be actually -msoft-float  ^^
That should insert calls to a library, which will break the build if it
actually happens.

Thanks,
          Dmitry


More information about the CRIU mailing list