[racket-dev] error with futures and the compiler
The attached program works fine, and if compiled, it works fine with small inputs: [samth@punge] r tst.rkt 40 /dev/null [samth@punge] r tst.rkt 4000 /dev/null [samth@punge] raco make tst.rkt [samth@punge] r tst.rkt 40 /dev/null But with big inputs, when compiled, it fails: [samth@punge] r tst.rkt 4000 /dev/null compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] === context === raise called (with non-exception value) by exception handler: #f; original exception raised: compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] internal error: failure during atomic Aborted -- sam th sa...@ccs.neu.edu tst.rkt Description: Binary data _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] error with futures and the compiler
Are the unsafe operations ever misapplied? Robby On Tue, Sep 20, 2011 at 4:27 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: The attached program works fine, and if compiled, it works fine with small inputs: [samth@punge] r tst.rkt 40 /dev/null [samth@punge] r tst.rkt 4000 /dev/null [samth@punge] raco make tst.rkt [samth@punge] r tst.rkt 40 /dev/null But with big inputs, when compiled, it fails: [samth@punge] r tst.rkt 4000 /dev/null compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] === context === raise called (with non-exception value) by exception handler: #f; original exception raised: compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] internal error: failure during atomic Aborted -- sam th sa...@ccs.neu.edu _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] error with futures and the compiler
Here's a rather smaller version, with the same error: #lang racket/base (require racket/future racket/flonum racket/fixnum racket/cmdline) (define N (command-line #:args (n) (string-number n))) (define (M Ci) (let loop ([Zr 0.0]) (fl+ 0. Ci) (loop 0.0))) (for ([y N]) (future (λ () (let loop-x () (fx 0 N) (M 1.1) (loop-x) On Tue, Sep 20, 2011 at 5:36 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: Removing the unsafe operations doesn't change the error. On Tue, Sep 20, 2011 at 5:29 PM, Robby Findler ro...@eecs.northwestern.edu wrote: Are the unsafe operations ever misapplied? Robby On Tue, Sep 20, 2011 at 4:27 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: The attached program works fine, and if compiled, it works fine with small inputs: [samth@punge] r tst.rkt 40 /dev/null [samth@punge] r tst.rkt 4000 /dev/null [samth@punge] raco make tst.rkt [samth@punge] r tst.rkt 40 /dev/null But with big inputs, when compiled, it fails: [samth@punge] r tst.rkt 4000 /dev/null compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] === context === raise called (with non-exception value) by exception handler: #f; original exception raised: compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] internal error: failure during atomic Aborted -- sam th sa...@ccs.neu.edu _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev -- sam th sa...@ccs.neu.edu -- sam th sa...@ccs.neu.edu _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] error with futures and the compiler
Fix pushed. At Tue, 20 Sep 2011 17:57:01 -0400, Sam Tobin-Hochstadt wrote: Here's a rather smaller version, with the same error: #lang racket/base (require racket/future racket/flonum racket/fixnum racket/cmdline) (define N (command-line #:args (n) (string-number n))) (define (M Ci) (let loop ([Zr 0.0]) (fl+ 0. Ci) (loop 0.0))) (for ([y N]) (future (λ () (let loop-x () (fx 0 N) (M 1.1) (loop-x) On Tue, Sep 20, 2011 at 5:36 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: Removing the unsafe operations doesn't change the error. On Tue, Sep 20, 2011 at 5:29 PM, Robby Findler ro...@eecs.northwestern.edu wrote: Are the unsafe operations ever misapplied? Robby On Tue, Sep 20, 2011 at 4:27 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: The attached program works fine, and if compiled, it works fine with small inputs: [samth@punge] r tst.rkt 40 /dev/null [samth@punge] r tst.rkt 4000 /dev/null [samth@punge] raco make tst.rkt [samth@punge] r tst.rkt 40 /dev/null But with big inputs, when compiled, it fails: [samth@punge] r tst.rkt 4000 /dev/null compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] === context === raise called (with non-exception value) by exception handler: #f; original exception raised: compiled/tst_rkt.zo::6943: read (compiled): ill-formed code [../../../racket/gc2/../src/read.c:4751] internal error: failure during atomic Aborted -- sam th sa...@ccs.neu.edu _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev -- sam th sa...@ccs.neu.edu -- sam th sa...@ccs.neu.edu _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
