| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2018-06-18 | Update copyright year | Henrik Nord | |
| 2018-01-26 | Eliminate get_list/3 internally in the compiler | Björn Gustavsson | |
| Instructions that produce more than one result complicate optimizations. get_list/3 is one of two instructions that produce multiple results (get_map_elements/3 is the other). Introduce the get_hd/2 and get_tl/2 instructions that return the head and tail of a cons cell, respectively, and use it internally in all optimization passes. For efficiency, we still want to use get_list/3 if both head and tail are used, so we will translate matching pairs of get_hd and get_tl back to get_list instructions. | |||
| 2018-01-22 | Don't build a stacktrace if it's only passed to erlang:raise/3 | Björn Gustavsson | |
| Consider the following function: function({function,Name,Arity,CLabel,Is0}, Lc0) -> try %% Optimize the code for the function. catch Class:Error:Stack -> io:format("Function: ~w/~w\n", [Name,Arity]), erlang:raise(Class, Error, Stack) end. The stacktrace is retrieved, but it is only used in the call to erlang:raise/3. There is no need to build a stacktrace in this function. We can avoid the building if we introduce an instruction called raw_raise/3 that works exactly like the erlang:raise/3 BIF except that its third argument must be a raw stacktrace. | |||
| 2017-11-30 | Add syntax in try/catch to retrieve the stacktrace directly | Björn Gustavsson | |
| This commit adds a new syntax for retrieving the stacktrace without calling erlang:get_stacktrace/0. That allow us to deprecate erlang:get_stacktrace/0 and ultimately remove it. The problem with erlang:get_stacktrace/0 is that it can keep huge terms in a process for an indefinite time after an exception. The stacktrace can be huge after a 'function_clause' exception or a failed call to a BIF or operator, because the arguments for the call will be included in the stacktrace. For example: 1> catch abs(lists:seq(1, 1000)). {'EXIT',{badarg,[{erlang,abs, [[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20|...]], []}, {erl_eval,do_apply,6,[{file,"erl_eval.erl"},{line,674}]}, {erl_eval,expr,5,[{file,"erl_eval.erl"},{line,431}]}, {shell,exprs,7,[{file,"shell.erl"},{line,687}]}, {shell,eval_exprs,7,[{file,"shell.erl"},{line,642}]}, {shell,eval_loop,3,[{file,"shell.erl"},{line,627}]}]}} 2> erlang:get_stacktrace(). [{erlang,abs, [[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22, 23,24|...]], []}, {erl_eval,do_apply,6,[{file,"erl_eval.erl"},{line,674}]}, {erl_eval,expr,5,[{file,"erl_eval.erl"},{line,431}]}, {shell,exprs,7,[{file,"shell.erl"},{line,687}]}, {shell,eval_exprs,7,[{file,"shell.erl"},{line,642}]}, {shell,eval_loop,3,[{file,"shell.erl"},{line,627}]}] 3> We can extend the syntax for clauses in try/catch to optionally bind the stacktrace to a variable. Here is an example using the current syntax: try Expr catch C:E -> Stk = erlang:get_stacktrace(), . . . In the new syntax, it would look like: try Expr catch C:E:Stk -> . . . Only a variable (not a pattern) is allowed in the stacktrace position, to discourage matching of the stacktrace. (Matching would also be expensive, because the raw format of the stacktrace would have to be converted to the cooked form before matching.) Note that: try Expr catch E -> . . . is a shorthand for: try Expr catch throw:E -> . . . If the stacktrace is to be retrieved for a throw, the 'throw:' prefix must be explicitly included: try Expr catch throw:E:Stk -> . . . | |||
| 2017-06-14 | Update copyright year | Hans Nilsson | |
| 2017-05-19 | genop.tab: Add an OTP 20 comment | Björn Gustavsson | |
| Make it clear that is_tagged_tuple/4 was added in OTP 20 (not R17). | |||
| 2017-03-24 | compiler: Add is_tagged_tuple instruction | Björn-Egil Dahlberg | |
| Rewrite the instruction stream on tagged tuple tests. Tagged tuples means a tuple of any arity with an atom as its first element. Typically records, ok-tuples and error-tuples. from: ... {test,is_tuple,Fail,[Src]}. {test,test_arity,Fail,[Src,Sz]}. ... {get_tuple_element,Src,0,Dst}. ... {test,is_eq_exact,Fail,[Dst,Atom]}. ... to: ... {test,is_tagged_tuple,Fail,[Src,Sz,Atom]}. ... | |||
| 2016-03-15 | update copyright-year | Henrik Nord | |
| 2015-08-28 | Fix typo in call_last/3 spec | Constantin Rack | |
| 2015-08-25 | Fix typo | Constantin Rack | |
| 2015-08-24 | Fix typo: message to send is in x(1) not x(0) | Constantin Rack | |
| 2015-08-09 | Fix another small typo | Constantin Rack | |
| 2015-08-09 | Fix typo | Constantin Rack | |
| 2015-06-18 | Change license text to APLv2 | Bruce Yinhe | |
| 2014-02-13 | compiler: Change map instructions for fetching values | Björn-Egil Dahlberg | |
| * Combine multiple get values with one instruction * Combine multiple check keys with one instruction | |||
| 2014-01-28 | compiler: Implement different instructions for => and := | Björn Gustavsson | |
| 2014-01-28 | Implement support for maps in the compiler | Björn Gustavsson | |
| To make it possible to build the entire OTP system, also define dummys for the instructions in ops.tab. | |||
| 2013-09-04 | genop.tab: Add documentation for many BEAM instructions | Björn Gustavsson | |
| By Erik Stenman (happi) with corrections by me. | |||
| 2011-12-09 | Update copyright years | Björn-Egil Dahlberg | |
| 2011-08-16 | compiler, emulator: Introduce the line/1 instruction | Björn Gustavsson | |
| Introduce the line/1 instruction in the compiler and the BEAM virtual machine. It will not yet be generated by the compiler and will not actually carry any information. | |||
| 2010-05-20 | Remove the bs_bits_to_bytes/3 instruction | Björn Gustavsson | |
| The last compiler to generate code that uses the bs_bits_to_bytes/3 instruction was the R11 compiler. Since we don't support loading R11 *.beam files in R14, removing the remaining support for the instruction. | |||
| 2010-05-17 | Add guard BIFs binary_part/2,3 | Patrik Nyblom | |
| Add the gc_bif's to the VM. Add infrastructure for gc_bif's (guard bifs that can gc) with two and. three arguments in VM (loader and VM). Add compiler support for gc_bif with three arguments. Add compiler (and interpreter) support for new guard BIFs. Add testcases for new guard BIFs in compiler and emulator. | |||
| 2010-05-11 | Introduce the new recv_mark/1 and recv_mark/1 instructions | Björn Gustavsson | |
| Make the recv_mark/1 and recv_mark/1 instructions known to the compiler and run-time system. For the moment, make the loader ignore any occurrences of those instructions in BEAM files. Also update hipe_beam_to_icode to ignore those instructions. | |||
| 2010-03-25 | Merge branch 'bg/compiler-remove-r11-support' into dev | Erlang/OTP | |
| * bg/compiler-remove-r11-support: compiler: Don't support the no_binaries option erts: Don't support the put_string/3 instruction compiler: Don't support the no_constant_pool option compiler: Don't support the r11 option test_server: Don't support communication with R11 nodes binary_SUITE: Don't test bit-level binary roundtrips with R11 nodes erts: Test compatibility of funs with R12 instead of R11 OTP-8531 bg/compiler-remove-r11-support | |||
| 2010-03-22 | erts: Don't support the put_string/3 instruction | Björn Gustavsson | |
| Since R14 does not need to load code that can also be loaded in an R11 run-time system, support for the put_string/3 instruction can be removed. | |||
| 2009-11-20 | The R13B03 release.OTP_R13B03 | Erlang/OTP | |
 |
index : otp.git | |
| Mirror of Erlang/OTP repository. | OTP Team |
| aboutsummaryrefslogtreecommitdiffstats |