--- !ditz.rubyforge.org,2008-03-06/issue 
title: compiler SETTEMP() does not update temp_max
desc: |-
  This has the side effect that if a SETTEMP() happens to be the highest value
  ever used, temp_max may be too low.
  
  This causes e.g. the bug: test-dev-bug-func-nargs-nregs.js.
  
  The fix is to either change SETTEMP() to update temp_next and check whether
  temp_max also needs to be bumped (which changes all SETTEMP() inline code
  to calls, with some code expansion), or all SETTEMP() locations need to be
  checked whether they need an explicit check for temp_max.
type: :bugfix
component: duk
release: v0.2
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2013-02-26 09:43:27.849051 Z
references: []

id: 12f3fcbbfec4e6e3829dcf19b19c4a654ded6696
log_events: 
- - 2013-02-26 09:43:28.238012 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2013-02-26 11:45:13.570119 Z
  - sva <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - |-
    Fixed by adding SETTEMP_CHECKMAX() which is used only during pass 2
    argument setup code.