Age | Commit message (Collapse) | Author | |
---|---|---|---|
2015-04-15 | Raise more descriptive error messages for failed map operations | Björn Gustavsson | |
According to EEP-43 for maps, a 'badmap' exception should be generated when an attempt is made to update non-map term such as: <<>>#{a=>42} That was not implemented in the OTP 17. José Valim suggested that we should take the opportunity to improve the errors coming from map operations: http://erlang.org/pipermail/erlang-questions/2015-February/083588.html This commit implement better errors from map operations similar to his suggestion. When a map update operation (Map#{...}) or a BIF that expects a map is given a non-map term, the exception will be: {badmap,Term} This kind of exception is similar to the {badfun,Term} exception from operations that expect a fun. When a map operation requires a key that is not present in a map, the following exception will be raised: {badkey,Key} José Valim suggested that the exception should be {badkey,Key,Map}. We decided not to do that because the map could potentially be huge and cause problems if the error propagated through links to other processes. For BIFs, it could be argued that the exceptions could be simply 'badmap' and 'badkey', because the bad map and bad key can be found in the argument list for the BIF in the stack backtrace. However, for the map update operation (Map#{...}), the bad map or bad key will not be included in the stack backtrace, so that information must be included in the exception reason itself. For consistency, the BIFs should raise the same exceptions as update operation. If more than one key is missing, it is undefined which of keys that will be reported in the {badkey,Key} exception. | |||
2015-03-13 | hipe: Fix maps sort order testcase | Björn-Egil Dahlberg | |
2014-04-29 | Add five new test files for maps in the HiPE test suite | Kostis Sagonas | |
2014-04-29 | Copy the tests for maps from the compiler application to a new HiPE test suite | Magnus Lång | |
Change the maps_guard_fun test to accept the HiPE trace format. | |||
2014-03-23 | Add support for testing the LLVM backend too | Kostis Sagonas | |
2014-03-23 | Ensure generated modules are properly included in the Emakefile | Kostis Sagonas | |
2014-02-24 | Up the time limit (globally) for some slow machines | Kostis Sagonas | |
2014-02-24 | Add check so that tests are skipped if HiPE is not available | Kostis Sagonas | |
2014-02-24 | Add a Makefile for the HiPE tests | Kostis Sagonas | |
2014-02-24 | Add tests for the HiPE compiler (Part 1: binaries and bitstrings) | Kostis Sagonas | |
Create tests for the HiPE native code compiler. This is the first part of the effort and contains tests that check that the native code produced by the HiPE compiler for binaries and bitstrings is OK and behaves similarly to the code produced by the BEAM compiler. | |||
2014-02-24 | Disable hipe_SUITE when environment doesn't support it | Tobias Schlager | |
2014-02-24 | Make hipe non-upgradable by setting appup file empty | Tobias Schlager | |
The reason for this is that if you are running a system with native compiled code, then you will have major problems with soft upgrade and the only reasonable way to go is to restart your emulator. Currently there is no instruction that will force ONLY a restart of the emulator, so the solution would be to hand write a relup with only a restart_emulator instruction. By letting hipe.appup be empty, systools will complain and not generate a relup - which should indicate that you might have to write your relup by hand. | |||
2014-02-24 | Add test suites performing app and appup file checks | Tobias Schlager | |
Add the mentioned test suites for *all* library and touched non-library applications. |