| Age | Commit message (Collapse) | Author |
|
|
|
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
'mrb_int' to 'int', possible loss of data
|
|
'int', possible loss of data
|
|
'int', possible loss of data
|
|
'long', possible loss of data
|
|
array in struct/union
|
|
'int', possible loss of data
|
|
'int', possible loss of data
|
|
array in struct/union
|
|
'mrb_int' to 'int', possible loss of data
|
|
implicitly converted to 64 bits (was 64-bit shift intended?)
|
|
'mrb_int' to 'mrb_float', possible loss of data
|
|
to 'int', possible loss of data
|
|
'int', possible loss of data
|
|
to 'khint_t', possible loss of data
|
|
'khint_t', possible loss of data
|
|
'khint_t', possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
possible loss of data
|
|
'int', possible loss of data
|
|
to 'uint16_t', possible loss of data
|
|
to 'uint16_t', possible loss of data
|
|
'int', possible loss of data
|
|
'int', possible loss of data
|
|
'int', possible loss of data
|
|
'int', possible loss of data
|
|
conversion from 'mrb_int' to 'int', possible loss of data
|
|
|
|
|
|
After f68f5f6, the operand of `OP_EPOP` should have been `1`.
Now we have removed the limitation.
|
|
fix #3809
|
|
|
|
If `#initialize` is implemented in C, we don't need stack consuming
`mrb_funcall`.
|
|
|
|
|
|
Instead of `irep -> proc` chain, we use `irep -> irep` chain to
avoid GC bugs like #3804. We added `target_class` reference to
`mrb_irep` struct. That means one more word consumption per `irep`.
|
|
|
|
ternary if statements with attributions.
|
|
It may be better to raise exceptions, but CRuby doesn't.
|