issue-54a2922eacf4511065643bdf825d5c156b858d84.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: "clobber warning: duk_js_call.c:643:12: warning: variable \xE2\x80\x98idx_func\xE2\x80\x99 might be clobbered by \xE2\x80\x98longjmp\xE2\x80\x99 or \xE2\x80\x98vfork\xE2\x80\x99 [-Wclobbered]"
desc: ""
type: :task
component: duk
release: v1.1
reporter: Sami Vaarala <sami.vaarala@iki.fi>
status: :unstarted
disposition: 
creation_time: 2014-07-11 00:26:35.301699 Z
references: []

id: 54a2922eacf4511065643bdf825d5c156b858d84
log_events: 
- - 2014-07-11 00:26:37.486903 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-07-11 00:26:51.112678 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - commented
  - Can be reproduced by compiling example eventloop.
- - 2014-08-14 08:07:38.848040 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - commented
  - |-
    idx_func is only assigned prior to setjmp(), not after setjmp(), so it should retain
    its value when longjmp() happens.  The warning appears spurious.  There have been
    spurious clobber warnings from gcc before, so perhaps this is gcc version specific.
- - 2014-08-14 08:10:33.903731 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v1.0 from v0.12
  - ""
- - 2014-10-13 15:37:13.437614 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v1.1 from v1.0
  - ""