Changes between Version 122 and Version 123 of GSoC/2017

Timestamp:

08/02/17 15:13:32 (7 years ago)

Author:

Cillian O'Donnell

Comment:

--

GSoC/2017

@@ -105 +105 @@
 * July 26
   * This week I worked on what needs to be changed before merging. I made too many changes to my main branch and broke what I had and couldn't recover. I learned a good lesson, make a branch for every small change, don't merge until fully tested and never break anything that's already working.. :) So I started again and got back to where I was fairly quickly. I fixed almost all the issues mentioned by Chris, added BSD license, remove camelCase, use error class, remove unit tests, move the coverage option out of options.py and in general match the style that is there. I just need to hear back from him about the log output and I'm having trouble getting my global _coverage macro back working without options.py. In the mean-time I will look at the covoar lock-up problem, I'm thinking I'll try and attach gdb to the process once I get it to lock-up again and then have a look around. On the plus side of having to start again, the lock-up happens less frequently and the output was cleaned up a bit, so it turned out to be a good thing.
+* Aug 2:
+  * This week I got the _coverage macro back working and inadvertently fixed the lock-up problem by getting everything prepared for the merge. There was an issue with symbols differing in size from jump tables being added to the end of them in some <test>.exe objdump's. I cleared up the error messages and the size discrepancy by adding another symbol ending possibility '_end'. Unfortunately I just realised this morning that it cleared up the messages but there is no branch info in the reports now. It must be chopping things up in other places as well. Back to the drawing board with this one. I'll have to find a more focused check for the jump tables. Also Chris took a second look at the code and gave a thorough review, I'm working through his list of points at the moment.
 
 == Denis Obrezkov ==