Permalink
Browse files

Restore both heap sizes to their maximum possible values.

  • Loading branch information...
1 parent dd0667f commit 5f6b20fec80b9e0cebf87d59ebbb014cd572f7a8 @stamourv committed Sep 12, 2011
Showing with 2 additions and 2 deletions.
  1. +2 −2 vm/include/heap.h
View
@@ -27,11 +27,11 @@
#include <arch/memory.h>
-#define MAX_VEC_ENCODING 1680
+#define MAX_VEC_ENCODING 8191
#define MIN_VEC_ENCODING 0
#define VEC_BYTES ((MAX_VEC_ENCODING - MIN_VEC_ENCODING + 1)*4)
-#define MAX_RAM_ENCODING 1680
+#define MAX_RAM_ENCODING 8191
#define MIN_RAM_ENCODING 1280
#define RAM_BYTES ((MAX_RAM_ENCODING - MIN_RAM_ENCODING + 1)*4)

2 comments on commit 5f6b20f

Contributor

whitequark commented on 5f6b20f Sep 12, 2011

This will actually fail on my ARM, as ram_init_heap() tries to write to the cell corresponding to MAX_RAM_ENCODING.

Owner

stamourv replied Sep 12, 2011

I understand that.
I made that change to make sure using the maximum values still worked (it doesn't without the previous commit).
I figured that your encoding configuration changes would override it, and that you wouldn't be affected.
Once your encoding configuration patches are merged, this will be in the host config, so you should be fine.

Please sign in to comment.