An error occurred fetching the project authors.
  1. 11 Feb, 2016 1 commit
  2. 04 Feb, 2016 1 commit
  3. 18 Nov, 2015 1 commit
  4. 06 Nov, 2015 2 commits
  5. 02 Nov, 2015 2 commits
    • Kevin Modzelewski's avatar
      6e81dc4f
    • Kevin Modzelewski's avatar
      Rename CLFunction->FunctionMetadata · c8360f6d
      Kevin Modzelewski authored
      and a couple of the other related functions:
      - addRTFunction is now an overload of FunctionMetadata::addVersion
      - boxFunctionMetadata is now createFunctionFromMetadata (it doesn't return a box)
      - createRTFunction was just a wrapper around new FunctionMetadata(), so get rid of it
      - boxRTFunction is now FunctionMetadata::create
      
      "CLFunction" never really made sense as a name, and some of the other related functions
      didn't make sense either (especially after a couple refactorings happened).  Hopefully
      this makes it less confusing.
      c8360f6d
  6. 04 Oct, 2015 1 commit
  7. 16 Sep, 2015 1 commit
    • Kevin Modzelewski's avatar
      Match cpython's HEAPTYPE flag · 3b40ed33
      Kevin Modzelewski authored
      It's supposed to mean "whether this type is heap allocated", but
      it gets used as "is this a builtin/extension type".  We heap-allocate
      our builtin types so we were setting HEAPTYPE, but this keeps on
      causing issues.  I don't think anything actually uses HEAPTYPE to mean
      it's on the stack or heap, so let's just set them all to be HEAPTYPE=0.
      
      For better or worse, I ended up implementing this by changing the builtin
      types from BoxedHeapClasses to BoxedClasses, which seems to make sense.
      This had the effect of changing the existence of the tp_as_foo structs,
      which get automatically created for HeapClasses but not for non-heap classes.
      So most of the changes in this commit are trying to make sure that we
      have those when CPython has them.
      3b40ed33
  8. 09 Sep, 2015 1 commit
    • Kevin Modzelewski's avatar
      Allow changing the number of default arguments · df2808da
      Kevin Modzelewski authored
      We already supported changing the values, but not the number
      of them.  The main trickiness here is
      - We had been assuming that the number of defaults was immutable,
        so I had to find the places that we used it and add invalidation.
      - We assumed that all functions based on the same source function would
        have the same number of defaults.
      
      For the first one, I found all the places that looked at the defaults array,
      which should hopefully be all the places that need invalidation.
      
      One tricky part is that we will embed the num_defaults data into code produced
      by the LLVM tier, and we currently don't have any mechanism for invalidating
      those functions.  This commit side-steps around that since the only functions that
      we can inline are the builtins, and those you aren't allowed to change the defaults
      anyway.  So I added a "can_change_defaults" flag.
      
      For the second part, I moved "num_defaults" from the CLFunction (our "code" object)
      to the BoxedFunction (our "function" object), and then changed the users to pull
      it from there.
      df2808da
  9. 29 Aug, 2015 1 commit
  10. 12 Aug, 2015 1 commit
  11. 11 Aug, 2015 1 commit
  12. 04 Aug, 2015 1 commit
  13. 03 Aug, 2015 1 commit
  14. 24 May, 2015 1 commit
  15. 16 Apr, 2015 1 commit
  16. 05 Feb, 2015 1 commit
  17. 09 Jan, 2015 1 commit
    • Kevin Modzelewski's avatar
      Add "noexcept" specifications to all C API endpoints · 91321622
      Kevin Modzelewski authored
      Add a PYSTON_NOEXCEPT define that gets defined to "noexcept" in C++ mode,
      and to the empty string in C mode.
      
      I don't think 'extern "C"' implies noexcept.
      
      This is partly for better performance when we know that a function cannot throw
      an exception, but also as an annotation for us since the exception model is
      the main difference between C land and Pyston land.
      
      Vim substitution: %s/\(\<PyAPI_FUNC\>(.*).*(\([^)]\|\n\)*)\);/\1 PYSTON_NOEXCEPT;/gc
      - This will catch almost all cases, except for functions not marked with PyAPI_FUNC
        and function definitions that have extra paretheses (in comments, usually)
      91321622
  18. 05 Jan, 2015 1 commit
  19. 18 Dec, 2014 2 commits
  20. 14 Dec, 2014 1 commit
  21. 29 Oct, 2014 1 commit
  22. 15 Oct, 2014 1 commit
    • Kevin Modzelewski's avatar
      Separate the CompilerType objects from the class definitions · 204b1da6
      Kevin Modzelewski authored
      Most code wants to have access to the basic types (INT, STR, etc)
      but doesn't need to know anything about what methods they support.
      
      Move the commonly-accessed parts of compvars.h into the always-included
      core/types.h, and remove almost all of the includes of compvars.h
      204b1da6
  23. 08 Sep, 2014 1 commit
  24. 27 Aug, 2014 1 commit
  25. 23 Aug, 2014 1 commit
  26. 22 Aug, 2014 1 commit