Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on May 20, 2010
  1. Set the stack start and size properly in a thread. @bugfix

    Evan Phoenix authored
  2. Make sure the arguments are Strings. @bugfix

    Evan Phoenix authored
  3. @brixen

    Updated CI tags for rubyspec sync.

    brixen authored Evan Phoenix committed
  4. @brixen

    Updated CI specs to RubySpec 2396c9fe.

    brixen authored Evan Phoenix committed
  5. @kronos

    Repair Bignum#divmod for cases with negative numbers. Fixes #319.

    kronos authored Evan Phoenix committed
  6. @kronos

    More specs for Bignum#divmod

    kronos authored Evan Phoenix committed
Commits on May 19, 2010
  1. Flesh out C-API to compile ImageMagick. Fixes #294.

    Evan Phoenix authored
  2. @brixen

    Fixed Bignum#<<, #>> specs.

    brixen authored
  3. @brixen

    Fixed Fixnum#[] specs.

    brixen authored
  4. @brixen

    Fixed Fixnum and Bignum bit shifts.

    brixen authored
    MRI does not implement Integer#>>, #<<. Removing those methods
    and making Bignum and Fixnum more explicit is better code.
  5. @brixen
  6. @brixen

    Fixed Fixnum#>> specs.

    brixen authored
    Removed the specs that test for a RangeError. Here's why:
    
    * In MRI, the C function that does the main work of #<< converts
      an argument to fit in a C long type. The C long type encodes a
      max value that is bigger than a Fixnum. So there are a range of
      Bignums > max fixnum but <= max C long that can be passed as an
      argument to #<< or #>> when the argument is negative. Since this
      boundary is not visible in any Ruby type, and is essentially an
      implementation detail where Fixnums are tagged pointers, these
      behaviors are left undefined in RubySpec.
    * The behavior of checking for a RangeError is not symmetric between
      #<< and #>>. Since #>> with negative argument is equivalent to
      calling #<< with positive argument, when to check and when not to
      check for RangeError becomes very twisty in the code. Both methods
      should have a precondition that the argument is a Fixnum.
  7. @kronos
  8. Teach Signal.trap the rest of it's tricks. Fixes #314.

    Evan Phoenix authored
  9. Disable ability to clone/dup Class objects. Fixes #316.

    Evan Phoenix authored
  10. Remove unnecessary test

    Evan Phoenix authored
  11. Add missing header files to scan for mode_t

    Evan Phoenix authored
  12. @kronos @brixen

    Fix left shifting for fixnums

    kronos authored brixen committed
  13. @brixen

    Fixed Fixnum#<< specs.

    brixen authored
  14. @brixen
  15. Appease the GCC deities.

    Evan Phoenix authored
  16. Handle object_id's for immediates. Fixes #315.

    Evan Phoenix authored
  17. Be persistant with write(2)

    Evan Phoenix authored
    On linux, write(2) seems to always result in a short write if the
    requested bytes to write is greater than 64k. Do the normal loop to
    keep writing all the data properly.
  18. Add vim syntax file for instructions.def

    Evan Phoenix authored
Commits on May 18, 2010
  1. Provide builtin UBF macros

    Evan Phoenix authored
  2. Add simplicit rb_thread_blocking_region

    Evan Phoenix authored
  3. Fix fork to allow SystemExit through properly

    Evan Phoenix authored
  4. Use Kernel.exit! after a forked block returns. Fixes #289.

    Evan Phoenix authored
  5. Add missing symbols for curb

    Evan Phoenix authored
  6. Add stub of re.h

    Evan Phoenix authored
  7. Add rb_reg_regcomp

    Evan Phoenix authored
  8. Add hacked rb_iterate/rb_each

    Evan Phoenix authored
Something went wrong with that request. Please try again.