1. 15 Oct, 2015 3 commits
    • Kevin Modzelewski's avatar
      Reenable unboxed ints · affb88b1
      Kevin Modzelewski authored
      - Change INT to a type that remembers whether it was boxed or not.
      - We still need a way of specifying a plain unboxed int, so add a
      "phony" UNBOXED_INT.  UNBOXED_INT is not usable as a variable type,
      but can be used to specify argument and return types.  It's up to
      the receiver (irgen or type analysis) to convert UNBOXED_INT to
      a usable INT.  Right now that's only guarded with a number of
      asserts (and not through, say, the C++ type system).
      affb88b1
    • Kevin Modzelewski's avatar
      Another unboxed-vals test · 0ce6a6be
      Kevin Modzelewski authored
      This will fail even with the current workaround
      0ce6a6be
    • Kevin Modzelewski's avatar
      Merge pull request #964 from kmod/rewrite_failed · b871bc10
      Kevin Modzelewski authored
      Fix a rare 'assert R11 is not used' crash
      b871bc10
  2. 13 Oct, 2015 3 commits
  3. 12 Oct, 2015 2 commits
    • Marius Wachtler's avatar
      fix a very bad stack map bug where symbolic entries could end up having the wrong location offset · ede85e07
      Marius Wachtler authored
      My sym entry llvm stackmap patch contains a bug where it will emit stackmap entries with the wrong offset into the large constants array.
      The problem is that the code assumes that the symbolic stack map constants are emitted at the end of the constants array,
      but doen't take into consideration that "normal" large constants can be added after symbolic entries.
      Thereby making the assigned offsets point to the wrong constants.
      To fix this issue I'm calculating the offset for symbolic entries now at the very end when we know that the number of constants can't change anymore.
      A nicer fix would be to not emit the symbolic entries inside the large cosntants array but instead into a special one.
      But I think this is overkill for now and would like to todo this when the stackmap v2 code landed inside llvm in order to not have to implement it twice.
      ede85e07
    • Marius Wachtler's avatar
  4. 10 Oct, 2015 7 commits
  5. 09 Oct, 2015 1 commit
  6. 08 Oct, 2015 3 commits
  7. 07 Oct, 2015 6 commits
  8. 06 Oct, 2015 12 commits
  9. 05 Oct, 2015 1 commit
  10. 04 Oct, 2015 2 commits