On 2011-02-03, at 19:29 , chevalma@iro.umontreal.ca wrote:
Hmm, I had that error but then fixed it. Can you try doing a git pull, see if it happens on the latest commit?
I was working before I added my code to the file.
Or do you mean make test worked until you added your code to strings.js? If so, I guess we'll need to debug that. Probably your code does something on initialization (when strings.js is run) that our current code doesn't handle properly. Perhaps you can commit it in another branch and I can look at it with Erick tomorrow, figure out what causes the error.
The error is due to executing the tests at the end of the file, so I just commented them out for now and committed in the master branch. I was just surprised that strings.js gets pulled in while arrays.js doesn't.
Bruno
- Maxime
Hi,
Does strings.js need to be included by default in 'make test'? My current stdlib implementation is done (the test-on-top-of-v8 part, not the tachyon-with-iir part), but committing it would break the master branch. I get a bus error after tachyon attempts to compile it:
Parsing Tachyon source: "stdlib/strings.js" Generating IR for: "stdlib/strings.js" Performing IR lowering for: "stdlib/strings.js" Generating machine code for: "stdlib/strings.js" Linking machine code for: "stdlib/strings.js" Initializing standard library make: *** [test] Bus error
Any suggestions?
Bruno