un-determined behavior of asyncs

un-determined behavior of asyncs

[Chaos Eternal]

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

hi gurus,

I wrote a short code to inspect the behavior of asyncs,
and find that neither the running time nor the order of execution is determined,
in fact , i find that the execution order of asyncs are random.

I just want to understand whether this random execution order of
asyncs is designed or desired or not-specified ?

thanks, the code is attached, the output follows:

$ guile async.scm
t2
((13700 1136293857 1) (18024 1136289128 0) (11235 1136295519 4) (11375
1136295012 3) (11444 1136294540 2) (8011 1136297645 9) (7978
1136297254 8) (7932 1136296817 7) (7735 1136296394 6) (3380 1136295978
5))
t1
((4262 1136289128 0) (317 1136293857 1) (221 1136294540 2) (199
1136295012 3) (228 1136295519 4) (215 1136295978 5) (203 1136296394 6)
(183 1136296817 7) (191 1136297254 8) (214 1136297645 9))

[-- Attachment #2: async.scm --]
[-- Type: application/octet-stream, Size: 791 bytes --]


;;(use-modules (srfi srfi-18))
(use-modules (ice-9 threads))
(define mb (make-parameter '()))

(define some-thread 
  (call-with-new-thread
   (lambda ()
     (begin 
       (mb '())
       (let lp ((i 0)) (if (< i 500000000) (lp (+ 1 i))))
       (display 't2)
       (newline)
       (display (mb))
       (newline)))))

(let lp ((i 0)) (if (< i 50000000) (lp (+ 1 i))))

(define t1-res 
  (map
   (let ((t some-thread))
     (lambda (x)
       (let ((ct (get-internal-real-time)))
	 (system-async-mark
	  (lambda ()
	    (mb
	     (cons 
	      (list (- (get-internal-real-time) ct) ct x)
	      (mb)))
	    )
	  t)
	 (list (- (get-internal-real-time) ct) ct x))))
   (iota 10)))

;;(thread-join! some-thread)
(join-thread some-thread)
(display 't1)
(newline)
(display t1-res)
(newline)

Re: un-determined behavior of asyncs

[Andy Wingo]

On Mon 20 May 2013 16:44, Chaos Eternal <chaoseternal@shlug.org> writes:

> I just want to understand whether this random execution order of
> asyncs is designed or desired or not-specified ?

Your program has no synchronization so I am not sure what you expect it
to do.  There's not even any guarantee that the thread is running at
all, AFAICS.

You may have come upon a bug but I don't understand the test case very
well.

Andy
-- 
http://wingolog.org/