Merged to master at 6bcb6e04fc9b..a84d47b41e74 (from, to]

You can see the entire diff with 'git diff' or at
https://github.com/brho/akaros/compare/6bcb6e04fc9b...a84d47b41e74

(rebuild glibc)

Also, Gan, if you test that aggressive-fp-save branch, apply it to a
commit before this one (for instance 6bcb6e04fc9b).  Otherwise, it'll
appear to be fixed regardless of whether or not aggressive-fp-save
worked or not.

Barret


On 2016-08-23 at 17:56 Barret Rhoden <[email protected]> wrote:
> Hi -
> 
> Hopefully this fixes the XMM corruption problem, at least for now.  I
> haven't looked into why the aggressive save/restore didn't work yet,
> but this ought to get the VMs working again.  Let me know how badly
> it's broken.  =)
> 
> Barret
> 
> 
> 
> The following changes since commit 86109dc44d5a17f003b23c0ffc8dc92c9514e631:
> 
>   Fix shifting bug in radix_insert() (2016-08-19 15:57:18 -0400)
> 
> are available in the git repository at:
> 
>   [email protected]:brho/akaros.git xmm-fixup
> 
> for you to fetch changes up to 61f0df5f460da927e587cbe4c825b91a82277bf7:
> 
>   Stop using snprintf in write_hex_to_fd (XCC) (2016-08-23 17:52:04 -0400)
> 
> ----------------------------------------------------------------
> View this online at:
> https://github.com/brho/akaros/compare/86109dc44d5a...61f0df5f460d
> 
> ----------------------------------------------------------------
> Barret Rhoden (2):
>       Fix num_to_nibble()
>       Stop using snprintf in write_hex_to_fd (XCC)
> 
>  kern/drivers/dev/version.c                         |  4 +--
>  .../glibc-2.19-akaros/sysdeps/akaros/Versions      |  2 ++
>  .../sysdeps/akaros/plan9_sockets.c                 | 38 
> ++++++++++++++++++++--
>  .../sysdeps/akaros/sys/plan9_helpers.h             |  3 ++
>  4 files changed, 43 insertions(+), 4 deletions(-)

-- 
You received this message because you are subscribed to the Google Groups 
"Akaros" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to