otp.git - Mirror of Erlang/OTP repository.

Age	Commit message (Collapse)	Author
2012-11-07	compiler tests: Correct error in receive_SUITE:groups/0	Björn Gustavsson
	Commit c4375a62cfaabfd8de757f59714623ba1a8cb915 added a parallel group, but incorrectly, so no test cases at all were run in receive_SUITE.
2012-10-23	compiler: Run testcases in parallel	Björn Gustavsson
	Run testcases in parallel will make the test suite run slightly faster. Another reason for this change is that we want more testing of parallel testcase support in common_test.
2011-04-12	compiler tests: Reinstate ?MODULE macro in calls to test_lib:recompile/1	Björn Gustavsson
	In 3d0f4a3085f11389e5b22d10f96f0cbf08c9337f (an update to conform with common_test), in all test_lib:recompile(?MODULE) calls, ?MODULE was changed to the actual name of the module. That would cause test_lib:recompile/1 to compile the module with the incorrect compiler options in cloned modules such as record_no_opt_SUITE, causing worse coverage.
2011-03-11	Update copyright years	Björn-Egil Dahlberg

2011-02-17	Rename Suite Callback to Common Test Hook	Lukas Larsson

2011-02-17	Fix formatting for compiler	Lukas Larsson

2011-02-17	Add init_per_suite and end_per_suite	Lukas Larsson

2011-02-17	Add ts_install_scb to suite/0	Lukas Larsson

2011-02-17	Update compiler tests to conform with common_test standard	Lukas Larsson

2011-02-17	Update all fin_per_testcase to end_per_testcase.	Lukas Larsson

2010-10-12	beam_block: Do optimizations in the safe order	Björn Gustavsson
	Moving of allocation instructions upwards in the instruction stream (in order to enable further optimizations) in beam_block, is implemented with the assumption that if a register {x,X} contains a valid term, then all other x register with lower numbers than X also contain valid terms. That assumption is true after code generation. The beam_utils:live_opt/1 optimization, however, may invalidate that assumption. For instance, if a receive statement exports a variable that is used, but the return value of the receive statement is not used, then {x,1} but not {x,0} contains a valid term at the end of the receive statement. If the receive statement is followed by {bif,self,{f,0},[],{x,0}}. {test_heap,NumberOfWords,2}. moving the allocation upwards will produce {test_heap,NumberOfWords,2}. {bif,self,{f,0},[],{x,0}}. which will cause the beam_validator pass to scream loudly that {x,0} is not live at the test_heap instruction. Fix the problem by doing the optimizations in reverse order. Reported-by: Jim Engquist
2010-05-12	Merge branch 'bg/opt-receive' into dev	Erlang/OTP
	* bg/opt-receive: Test that gen_server:call/2,3 are fast even with a huge message queue erts: Add tests for the receive optimization Update primary bootstrap erts: Implement recv_mark/1 and recv_set/1 for real compiler tests: Cover the error handling code in beam_receive compiler test: Test optimization of receive statements Optimize selective receives in the presence of a large message queue Introduce the new recv_mark/1 and recv_mark/1 instructions Compile tests that communicate with R12 nodes with the r12 option Move p_run/2 to test_lib gen: Inline wait_resp_mon/2 to help the compiler optimize OTP-8623 bg/opt-receive reveive statements that can only read out a newly created reference are now specially optimized so that it will execute in constant time regardless of the number of messages in the receive queue for the process. That optimization will benefit calls to gen_server:call(). (See gen:do_call/4 for an example of a receive statement that will be optimized.)
2010-05-11	compiler test: Test optimization of receive statements	Björn Gustavsson
	We don't attempt to run the generated code, but use beam_disasm and check for the presence or absence (as appropriate) of the recv_mark/1 and recv_set/1 instructions.
2009-11-20	The R13B03 release.OTP_R13B03	Erlang/OTP