- Apr 02, 2016
- Mar 16, 2016
-
-
whh8b authored
When looking for a dollop entry's fallthrough, be sure to fallback and look at the dollop's fallthrough when the particular entry does not have one.
-
- Mar 08, 2016
-
-
jdh8d authored
-
- Mar 03, 2016
-
-
jdh8d authored
No commit message
-
- Feb 23, 2016
-
-
jdh8d authored
No commit message
-
- Feb 21, 2016
-
-
jdh8d authored
No commit message
-
- Feb 20, 2016
-
-
whh8b authored
-
whh8b authored
When a dollop with small fallthroughs would fit entirely in an allocated region but some of those fallthroughs are already placed, coalescing would miscalculate what to do. It would say, "Let's place it all" but would eventually want to put a jmp to the already-placed dollop. When the fallthoughs were small, that jump would be bigger than the entirety of dollop and cause us to overflow the reserved space.
-
- Feb 19, 2016
-
-
whh8b authored
-
- Feb 17, 2016
- Feb 14, 2016
-
-
whh8b authored
-
- Feb 13, 2016
- Feb 04, 2016
-
-
whh8b authored
-
- Feb 01, 2016
-
-
whh8b authored
1. A plugin that returns space smaller than "min size" is not bad if the dollop fits within the space entirely. 2. GetNearbyFreeRanges() should really treat the parameter as a lower bound.
-
- Jan 30, 2016
- Jan 28, 2016
- Jan 27, 2016
-
-
whh8b authored
-
- Jan 26, 2016
-
-
whh8b authored
-
- Jan 25, 2016
- Jan 24, 2016
- Jan 23, 2016
-
-
whh8b authored
Previous code calculated the dollop based on the comprising instructions' fallthrough. This is incorrect in the case where a dollop stops short (because it was split during placement, ran through an IBT, etc).
-
- Jan 21, 2016
-
-
whh8b authored
This is important for a number of reasons. Most importantly, however, is the fact that it will cause a problem with the push64 relocations calculations.
-
- Jan 19, 2016
-
-
whh8b authored
-