From afb632d2028fdc4a37e10e41e1929264ff59f52e Mon Sep 17 00:00:00 2001
From: Hans Bolinder
Forbid multiple values in Core Erlang sequence arguments.
- Thanks to José Valim and Anthony Ramine.
Own Id: OTP-10818
@@ -144,7 +144,7 @@
Own Id: OTP-10150
@@ -256,7 +256,7 @@Fix typo in `compile' doc: unmatched parenthesis (Thanks - to Ricardo Catalinas Jiménez)
+ to Ricardo Catalinas Jiménez)Own Id: OTP-9919
Using filter expressions containing
Own Id: OTP-8054
-- cgit v1.2.3 From e5875001247e6a6ac4f474157a51a8c54f94ae49 Mon Sep 17 00:00:00 2001 From: Hans BolinderA string describing the error is obtained with the following call:
--
cgit v1.2.3
From c011973178d860f280c6ce18b07ce4176aec5b35 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?=
Date: Fri, 6 Sep 2013 13:40:21 +0200
Subject: Change encoding of troublesome notes.xml files to utf-8
Most notes.xml files will be updated in every release and cause
the kind of the problems described in the previous commit.
---
lib/compiler/doc/src/notes.xml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index 33b32a3dce..837fcf4368 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -1,4 +1,4 @@
-
+
@@ -96,7 +96,7 @@
-
Forbid multiple values in Core Erlang sequence arguments.
- Thanks to José Valim and Anthony Ramine.
+ Thanks to José Valim and Anthony Ramine.
Own Id: OTP-10818
@@ -195,7 +195,7 @@
compile:forms/2 will now use a
{source,SourceFilePath} to set the source returned by
- module_info(compile) (Thanks to José Valim)
+ module_info(compile) (Thanks to José Valim)
Own Id: OTP-10150
@@ -307,7 +307,7 @@
-
Fix typo in `compile' doc: unmatched parenthesis (Thanks
- to Ricardo Catalinas Jiménez)
+ to Ricardo Catalinas Jiménez)
Own Id: OTP-9919
@@ -808,7 +808,7 @@
(Thanks to Paul Fisher.)
Using filter expressions containing andalso or
orelse in a list comprehension could cause a
- compiler crash. (Thanks to Martin Engström.)
+ compiler crash. (Thanks to Martin Engström.)
Own Id: OTP-8054
--
cgit v1.2.3
From 20641fe0f2ea745873fc7557448d3a7deb1bd639 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
Date: Mon, 16 Sep 2013 20:11:53 +0200
Subject: Prepare release
---
lib/compiler/doc/src/notes.xml | 61 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 61 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index 837fcf4368..eb5fa8b398 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -31,6 +31,67 @@
This document describes the changes made to the Compiler
application.
+Compiler 4.9.3
+
+ Fixed Bugs and Malfunctions
+
+ -
+
+ Expressions such as 'B = is_integer(V), if B and B
+ -> ok end' would crash the compiler.
+
+ Own Id: OTP-11240
+
+ -
+
+ compile:file2/2 with the option
+ report_errors could return ErrorInfo tuples with
+ only two elements, while the documentation says that the
+ ErrorInfo tuple always has three elements. Also updated
+ the documentation to add that the first element may be
+ 'none ' if no line number is applicable.
+
+ Own Id: OTP-11304 Aux Id: seq12412
+
+
+
+
+
+ Improvements and New Features
+
+ -
+
+ Fix matching of floating point middle-endian machines.
+ Thanks to Johannes Weissl.
+
+ Own Id: OTP-11201
+
+ -
+
+ Restrict inlining of local fun references. Thanks to
+ Anthony Ramine.
+
+ Own Id: OTP-11211
+
+ -
+
+ Silence a misleading warning with some comprehensions.
+ Thanks to Anthony Ramine.
+
+ Own Id: OTP-11212
+
+ -
+
+ Forbid returning a match context in beam_validator.
+ Thanks to Anthony Ramine.
+
+ Own Id: OTP-11247
+
+
+
+
+
+
Compiler 4.9.2
Fixed Bugs and Malfunctions
--
cgit v1.2.3
From d2b412df6c8751c10de025399cb04a8194169d0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jos=C3=A9=20Valim?=
Date: Fri, 18 Oct 2013 12:05:46 +0200
Subject: Allow all auto imports to be suppressed at once
This patch introduces the no_auto_import attribute:
-compile(no_auto_import).
Useful for code generation tools that always use the
qualified function names and want to avoid the auto
imported functions clashing with local ones.
Implementation wise, we chose to have a special flag
'all' to avoid doing many set lookups when checking for
suppression.
---
lib/compiler/doc/src/compile.xml | 5 +++++
1 file changed, 5 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/compile.xml b/lib/compiler/doc/src/compile.xml
index f1238f27a6..579612b531 100644
--- a/lib/compiler/doc/src/compile.xml
+++ b/lib/compiler/doc/src/compile.xml
@@ -402,6 +402,11 @@ module.beam: module.erl \
-compile({no_auto_import,[error/1]}).
+ no_auto_import
+ -
+
Do not auto import any functions from the module erlang .
+
+
no_line_info
-
--
cgit v1.2.3
From 25237481ccccd3ddfa74582dc267632ad618ba30 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
Date: Mon, 9 Dec 2013 20:12:33 +0100
Subject: Prepare release
---
lib/compiler/doc/src/notes.xml | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index eb5fa8b398..cb39b28d3d 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -31,6 +31,34 @@
This document describes the changes made to the Compiler
application.
+Compiler 4.9.4
+
+ Fixed Bugs and Malfunctions
+
+ -
+
+ Typo fix ambigous -> ambiguous. Thanks to Leo Correa.
+
+ Own Id: OTP-11455
+
+
+
+
+
+ Improvements and New Features
+
+ -
+
+ Lift 'after' blocks to zeroary functions. Thanks to
+ Anthony Ramine.
+
+ Own Id: OTP-11267
+
+
+
+
+
+
Compiler 4.9.3
Fixed Bugs and Malfunctions
--
cgit v1.2.3
From 18315c1675d965e5d0210a560e4742c483fcfd7f Mon Sep 17 00:00:00 2001
From: Tuncer Ayaz
Date: Tue, 3 Dec 2013 18:43:30 +0100
Subject: Officially support building assembler files
erlc is wired to treat *.S files as assembler and build them as
compile:file(File, [from_asm]), but this is not documented. There's also
a documented compile:file/2 option called 'asm' (mapping to 'from_asm'),
but the wording discourages its use. All of this has been in place and
in use for a long time. Therefore, it should be supported officially.
To fix that, make the following changes:
* document erlc handling of *.core files
* un-document 'asm' and document 'from_asm' instead
* deprecate 'asm'
While at it, fix a minor typo in the test suite.
---
lib/compiler/doc/src/compile.xml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/compile.xml b/lib/compiler/doc/src/compile.xml
index 73d75851cf..eb7745890e 100644
--- a/lib/compiler/doc/src/compile.xml
+++ b/lib/compiler/doc/src/compile.xml
@@ -350,12 +350,11 @@ module.beam: module.erl \
parsed code before the code is checked for errors.
- asm
+ from_asm
-
The input file is expected to be assembler code (default
file suffix ".S"). Note that the format of assembler files
- is not documented, and may change between releases - this
- option is primarily for internal debugging use.
+ is not documented, and may change between releases.
no_strict_record_tests
--
cgit v1.2.3
From 455c8238535d2754234cd68bbf7caba9960607d6 Mon Sep 17 00:00:00 2001
From: Tuncer Ayaz
Date: Tue, 3 Dec 2013 19:16:16 +0100
Subject: Officially support building core files
erlc is wired to treat *.core files as core and build them as
compile:file(File, [from_core]), but this is not documented. There's
also an udocumented compile:file/2 option called 'from_core'. This has
been in place and in use for a long time. Therefore, it should be
supported officially.
To fix that, make the following changes:
* document erlc handling of *.core files
* document 'from_core'
---
lib/compiler/doc/src/compile.xml | 7 +++++++
1 file changed, 7 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/compile.xml b/lib/compiler/doc/src/compile.xml
index eb7745890e..1459f696a0 100644
--- a/lib/compiler/doc/src/compile.xml
+++ b/lib/compiler/doc/src/compile.xml
@@ -357,6 +357,13 @@ module.beam: module.erl \
is not documented, and may change between releases.
+ from_core
+ -
+
The input file is expected to be core code (default
+ file suffix ".core"). Note that the format of core files
+ is not documented, and may change between releases.
+
+
no_strict_record_tests
-
This option is not recommended.
--
cgit v1.2.3
From 774955d0d2a44fa8ac5943a14516d54db2b8f6d5 Mon Sep 17 00:00:00 2001
From: Hans Bolinder
Date: Mon, 3 Mar 2014 15:27:09 +0100
Subject: Introduce compiler option 'nowarn_deprecated_type'
The deprecation of the built-in types dict/0 and so on had as
side-effect that it was impossible to switch to dict:dict/2 and so on
without getting warnings either in the the previous release (R16B) or
the current one (17.0).
By including the attribute
-compile(nowarn_deprecated_type).
in an Erlang source file warnings about deprecated types can be
avoided in 17.0.
The option can also be given as a compiler flag:
erlc +nowarn_deprecated_type file.erl
---
lib/compiler/doc/src/compile.xml | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/compile.xml b/lib/compiler/doc/src/compile.xml
index c66c8ea4bf..5fccdcdcb5 100644
--- a/lib/compiler/doc/src/compile.xml
+++ b/lib/compiler/doc/src/compile.xml
@@ -4,7 +4,7 @@
- 1996 2013
+ 1996 2014
Ericsson AB. All Rights Reserved.
@@ -551,6 +551,14 @@ module.beam: module.erl \
{Module,Name,Arity} or a list of such tuples.
+ nowarn_deprecated_type
+ -
+
Turns off warnings for uses of deprecated types. By
+ default (warn_deprecated_type ), warnings are
+ emitted for every use of a type known by the compiler
+ to be deprecated.
+
+
warn_obsolete_guard
-
Causes warnings to be emitted for calls to old type
--
cgit v1.2.3
From f719d0fe308f00b85f92c29d7cdf9b0dc20d98a2 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
Date: Mon, 7 Apr 2014 19:52:48 +0200
Subject: Update release notes
---
lib/compiler/doc/src/notes.xml | 227 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 227 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index cb39b28d3d..a0f2e617cb 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -31,6 +31,233 @@
This document describes the changes made to the Compiler
application.
+Compiler 5.0
+
+ Fixed Bugs and Malfunctions
+
+ -
+
+ Line numbers would not be correct when a binary
+ construction such as
+ '<<Bin/binary,...>> ' fails. (Thanks to
+ Stanislav Seletskiy for reporting this bug.)
+
+ Own Id: OTP-11572
+
+ -
+
+ The compiler now properly annotates the code in value in
+ the 'after ' clause for a 'try ' so that
+ Dialyzer no longer generates a false warning for an
+ unmatched return.
+
+ Own Id: OTP-11580
+
+ -
+
+ Some case statements where no clause would match could
+ cause an internal error in the compiler. (Thanks to Erik
+ Soe Sorensen for reporting this bug.)
+
+ Own Id: OTP-11610
+
+ -
+
+ With --Wunmatched_returns , dialyzer will no longer
+ warn when the value of a list comprehension is ignored,
+ provided that the each value in the list would be an
+ atomic value (such as integer or atoms, as opposed to
+ tuples and lists). Example: ignoring '[io:format(...)
+ || ...] ' will not cause a warning, while ignoring
+ '[file:close(Fd) || ...] ' will.
+
+ Own Id: OTP-11626
+
+ -
+
+ Matching out a binary and applying the binary as if it
+ were a fun would crash the run-time system. (Thanks to
+ Loïc Hoguin.)
+
+ Own Id: OTP-11672
+
+ -
+
+ Some local implementations of removing the last element
+ from a list are replaced by lists:droplast/1 . Note
+ that this requires at least stdlib-2.0 , which is
+ the stdlib version delivered in OTP 17.0. (Thanks to Hans
+ Svensson)
+
+ Own Id: OTP-11678
+
+ -
+
+ Allow all auto imports to be suppressed at once.
+ Introducing the no_auto_import attribute:
+ -compile(no_auto_import). Useful for code generation
+ tools that always use the qualified function names and
+ want to avoid the auto imported functions clashing with
+ local ones. (Thanks to José Valim.)
+
+ Own Id: OTP-11682
+
+ -
+
+ Application upgrade (appup) files are corrected for the
+ following applications:
+
+ asn1, common_test, compiler, crypto, debugger,
+ dialyzer, edoc, eldap, erl_docgen, et, eunit, gs, hipe,
+ inets, observer, odbc, os_mon, otp_mibs, parsetools,
+ percept, public_key, reltool, runtime_tools, ssh,
+ syntax_tools, test_server, tools, typer, webtool, wx,
+ xmerl
+
+ A new test utility for testing appup files is added to
+ test_server. This is now used by most applications in
+ OTP.
+
+ (Thanks to Tobias Schlager)
+
+ Own Id: OTP-11744
+
+ -
+
+ Adapt 'asm' deprecation message to new version scheme.
+ (Thanks to Tuncer Ayaz)
+
+ Own Id: OTP-11751
+
+ -
+
+ A number of compiler errors where unusual or nonsensical
+ code would crash the compiler have been reported by Ulf
+ Norell and corrected by Anthony Ramine.
+
+ Own Id: OTP-11770
+
+
+
+
+
+ Improvements and New Features
+
+ -
+
+ Compilation times for modules with a huge number for
+ record accesses using the dot operator has been improved.
+
+ Own Id: OTP-10652
+
+ -
+
+ The compiler can generate somewhat better code by moving
+ let expressions into sequences. (Thanks to Anthony
+ Ramine.)
+
+ Own Id: OTP-11056
+
+ -
+
+ Forbid unsized fields in patterns of binary generators
+ and simplified v3_core's translation of bit string
+ generators. (Thanks to Anthony Ramine.)
+
+ Own Id: OTP-11186
+
+ -
+
+ Funs can now be a given a name. Thanks to to Richard
+ O'Keefe for the idea (EEP37) and to Anthony Ramine for
+ the implementation.
+
+ Own Id: OTP-11537
+
+ -
+
+ Using the from_asm option to produce a BEAM file
+ starting from BEAM assembly code would often fail because
+ early optimization passes would not understand
+ instructions that later optimization passes would
+ introduce. (Thanks to Anthony Ramine.)
+
+ Own Id: OTP-11544
+
+ -
+
+ The .core and .S extensions are now
+ documented in the erlc documentation, and the
+ 'from_core ' and 'from_asm ' options are now
+ documented in the compiler documentation. (Thanks to
+ Tuncer Ayaz.)
+
+ Own Id: OTP-11547
+
+ -
+
Optimization of case expressions that build tuples or
+ lists have been improved.
+
+ Own Id: OTP-11584
+
+ -
+
+ EEP43: New data type - Maps
+
+ With Maps you may for instance: M0 =
+ #{ a => 1, b => 2}, % create
+ associations M1 = M0#{ a := 10 }, %
+ update values M2 = M1#{ "hi" =>
+ "hello"}, % add new associations #{
+ "hi" := V1, a := V2, b := V3} = M2. % match keys with
+ values
+
+ For information on how to use Maps please see the
+ Reference
+ Manual .
+
+ The current implementation is without the following
+ features: - No variable keys
+ - No single value access
- No map
+ comprehensions
+
+ Note that Maps is experimental during OTP 17.0.
+
+ Own Id: OTP-11616
+
+ -
+
+ Some function specs are corrected or moved and some edoc
+ comments are corrected in order to allow use of edoc.
+ (Thanks to Pierre Fenoll)
+
+ Own Id: OTP-11702
+
+ -
+
+ Thanks to Anthony Ramine for several improvements to the
+ optimizations in the BEAM compiler and for cleaning up
+ the code the code that transforms list and binary
+ comprehensions to Core Erlang.
+
+ Own Id: OTP-11720
+
+ -
+
+ The default encoding for Erlang source files is now
+ UTF-8. As a temporary measure to ease the transition from
+ the old default of latin-1, if the compiler encounters
+ byte sequences that are not valid UTF-8 sequences, the
+ compiler will re-try the compilation in latin-1 mode.
+ This workaround will be removed in a future release.
+
+ Own Id: OTP-11791
+
+
+
+
+
+
Compiler 4.9.4
Fixed Bugs and Malfunctions
--
cgit v1.2.3
From f47320f43c3fb39f78054834e60ae9424ac79f35 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn-Egil=20Dahlberg?=
Date: Tue, 17 Jun 2014 16:26:50 +0200
Subject: doc: Fix broken links
---
lib/compiler/doc/src/notes.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index a0f2e617cb..7b2b60fb3d 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -211,10 +211,10 @@
"hello"}, % add new associations
#{
"hi" := V1, a := V2, b := V3} = M2. % match keys with
values
-
- For information on how to use Maps please see the
- Reference
- Manual .
+
+ For information on how to use Maps please see Map Expressions in the
+
+ Reference Manual .
The current implementation is without the following
features: - No variable keys
--
cgit v1.2.3
From 77da984614ae462912a1896ba1bb73c798ffd4f8 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
Date: Thu, 19 Jun 2014 13:47:21 +0200
Subject: Prepare release
---
lib/compiler/doc/src/notes.xml | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index 7b2b60fb3d..55e9661d7d 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -31,6 +31,29 @@
This document describes the changes made to the Compiler
application.
+Compiler 5.0.1
+
+ Fixed Bugs and Malfunctions
+
+ -
+
+ A Dialyzer crash involving analysis of Map types has now
+ been fixed.
+
+ Own Id: OTP-11947
+
+ -
+
The compiler would fail to compile a file with a
+ latin-1 character in the false branch of an -ifdef
+ or -indef .
+
+ Own Id: OTP-11987
+
+
+
+
+
+
Compiler 5.0
Fixed Bugs and Malfunctions
--
cgit v1.2.3
From 950d808c97a4c5b579f4f1cc16b95f2d419d3505 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
Date: Mon, 15 Sep 2014 12:02:14 +0200
Subject: Update release notes
---
lib/compiler/doc/src/notes.xml | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index 55e9661d7d..d48a0a5599 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -31,6 +31,22 @@
This document describes the changes made to the Compiler
application.
+Compiler 5.0.2
+
+ Fixed Bugs and Malfunctions
+
+ -
+
+ Corrected a bug with incorrect code generation when
+ inlining was turned on.
+
+ Own Id: OTP-12132
+
+
+
+
+
+
Compiler 5.0.1
Fixed Bugs and Malfunctions
--
cgit v1.2.3
From 7f3486a5ddc02a366f2945dfd009c4a2697a2b98 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
Date: Tue, 9 Dec 2014 15:21:47 +0100
Subject: Prepare release
---
lib/compiler/doc/src/notes.xml | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index d48a0a5599..84ebd2f210 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -31,6 +31,35 @@
This document describes the changes made to the Compiler
application.
+Compiler 5.0.3
+
+ Fixed Bugs and Malfunctions
+
+ -
+
+ Named funs with the same name and arity could get mixed
+ up with each other.
+
+ Own Id: OTP-12262
+
+ -
+
+ Coalesce map keys in dialyzer mode
+
+ This fixes a regression introduced in commit
+ 805f9c89fc01220bc1bb0f27e1b68fd4eca688ba The problem
+ occurred with compounded map keys compiled with dialyzer
+ option turned on, '+dialyzer'.
+
+ Reported by: Ivan Uemlianin
+
+ Own Id: OTP-12347
+
+
+
+
+
+
Compiler 5.0.2
Fixed Bugs and Malfunctions
--
cgit v1.2.3
From 62870c998955e1498e71bfc90607885e96ecaa27 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
Date: Tue, 31 Mar 2015 12:24:04 +0200
Subject: Prepare release
---
lib/compiler/doc/src/notes.xml | 52 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 52 insertions(+)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/notes.xml b/lib/compiler/doc/src/notes.xml
index 84ebd2f210..9b5b44f3e1 100644
--- a/lib/compiler/doc/src/notes.xml
+++ b/lib/compiler/doc/src/notes.xml
@@ -31,6 +31,58 @@
This document describes the changes made to the Compiler
application.
+Compiler 5.0.4
+
+ Fixed Bugs and Malfunctions
+
+ -
+
+ Matching out a map from a record and then updating the
+ record could cause a 'badarg' exception at run-time.
+ (Thanks to Dmitry Aleksandrov for reporting this bug.)
+
+ Own Id: OTP-12402
+
+ -
+
The compiler would crash when compiling some complex,
+ nonsensical guards such as:
+ ... when {{X}}, -X ...
+
+ Own Id: OTP-12410
+
+ -
+
+ In rare circumstances, using binary pattern in the value
+ part of a map pattern would cause the compiler to crash.
+
+ Own Id: OTP-12414
+
+ -
+
Case expressions where a map was wrapped in a tuple or
+ list such as:
+ case {a,Map} of
{a,#{k:=_}}=Tuple ->
+ Tuple
end.
+ would be unsafely "optimized" to either cause an
+ exception at run-time or would return an empty map.
+
+ Own Id: OTP-12451
+
+ -
+
When a variable was compared to a literal map using
+ the '== ' operator, the compiler would change the
+ operator to '=:= ' since it is more efficient.
+ However, this optimization is not safe if the map literal
+ has numeric keys or values. The compiler will now only do
+ the optimization if all keys and values are
+ non-numeric.
+
+ Own Id: OTP-12456
+
+
+
+
+
+
Compiler 5.0.3
Fixed Bugs and Malfunctions
--
cgit v1.2.3
From 4823c4f7c792f8a9e4c27744f436f0f10763ef17 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?=
Date: Thu, 21 May 2015 12:23:48 +0200
Subject: Update compiler documentation
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Language cleaned up by the technical writer tmanevik from
Combitech. Proofreading and corrections by Björn Gustavsson.
---
lib/compiler/doc/src/compile.xml | 506 +++++++++++++++++++--------------------
lib/compiler/doc/src/ref_man.xml | 2 +-
2 files changed, 249 insertions(+), 259 deletions(-)
(limited to 'lib/compiler/doc/src')
diff --git a/lib/compiler/doc/src/compile.xml b/lib/compiler/doc/src/compile.xml
index 5fccdcdcb5..a271729c82 100644
--- a/lib/compiler/doc/src/compile.xml
+++ b/lib/compiler/doc/src/compile.xml
@@ -32,15 +32,15 @@
Erlang Compiler
This module provides an interface to the standard Erlang
- compiler. It can generate either a new file which contains
- the object code, or return a binary which can be loaded directly.
+ compiler. It can generate either a new file, which contains
+ the object code, or return a binary, which can be loaded directly.
file(File)
- Compile a file
+ Compiles a file.
Is the same as
file(File, [verbose,report_errors,report_warnings]) .
@@ -50,7 +50,7 @@
file(File, Options) -> CompRet
- Compile a file
+ Compiles a file.
CompRet = ModRet | BinRet | ErrRet
ModRet = {ok,ModuleName} | {ok,ModuleName,Warnings}
@@ -64,39 +64,38 @@
Returns {ok,ModuleName} if successful, or error
if there are errors. An object code file is created if
- the compilation succeeds with no errors. It is considered
+ the compilation succeeds without errors. It is considered
to be an error if the module name in the source code is
not the same as the basename of the output file.
- Here follows first all elements of Options that in
- some way control the behavior of the compiler.
+ Available options:
basic_validation
-
-
This option is fast way to test whether a module will
- compile successfully (mainly useful for code generators
- that want to verify the code they emit). No code will
+
This option is a fast way to test whether a module will
+ compile successfully. This is useful for code generators
+ that want to verify the code that they emit. No code is
generated. If warnings are enabled, warnings generated by
the erl_lint module (such as warnings for unused
- variables and functions) will be returned too.
+ variables and functions) are also returned.
- Use the strong_validation option to generate all
+
Use option strong_validation to generate all
warnings that the compiler would generate.
strong_validation
-
-
Similar to the basic_validation option, no code
- will be generated, but more compiler passes will be run
- to ensure also warnings generated by the optimization
- passes are generated (such as clauses that will not match
+
Similar to option basic_validation . No code
+ is generated, but more compiler passes are run
+ to ensure that warnings generated by the optimization
+ passes are generated (such as clauses that will not match,
or expressions that are guaranteed to fail with an
- exception at run-time).
+ exception at runtime).
binary
-
-
Causes the compiler to return the object code in a
+
The compiler returns the object code in a
binary instead of creating an object file. If successful,
the compiler returns {ok,ModuleName,Binary} .
@@ -105,7 +104,9 @@
-
The compiler will emit informational warnings about binary
matching optimizations (both successful and unsuccessful).
- See the Efficiency Guide for further information.
+ For more information, see the section about
+ bin_opt_info
+ in the Efficiency Guide.
compressed
@@ -117,20 +118,19 @@
debug_info
-
- Include debug information in the form of abstract code
+
Includes debug information in the form of abstract code
(see
The Abstract Format
in ERTS User's Guide) in the compiled beam module. Tools
- such as Debugger, Xref and Cover require the debug
- information to be included.
+ such as Debugger , Xref , and Cover require
+ the debug information to be included.
Warning: Source code can be reconstructed from
the debug information. Use encrypted debug information
- (see below) to prevent this.
+ (encrypt_debug_info ) to prevent this.
- See
- beam_lib(3)
- for details.
+ For details, see
+ beam_lib(3) .
{debug_info_key,KeyString}
@@ -138,65 +138,61 @@
{debug_info_key,{Mode,KeyString}}
-
- Include debug information, but encrypt it, so that it
+
Includes debug information, but encrypts it so that it
cannot be accessed without supplying the key. (To give
- the debug_info option as well is allowed, but is
+ option debug_info as well is allowed, but
not necessary.) Using this option is a good way to always
have the debug information available during testing, yet
- protect the source code.
+ protecting the source code.
Mode is the type of crypto algorithm to be used
- for encrypting the debug information. The default type --
- and currently the only type -- is des3_cbc .
- See
- beam_lib(3)
- for details.
+ for encrypting the debug information. The default
+ (and currently the only) type is des3_cbc .
+ For details, see
+ beam_lib(3) .
encrypt_debug_info
-
- Like the debug_info_key option above, except that
- the key will be read from an .erlang.crypt file.
+
Similar to the debug_info_key option, but
+ the key is read from an .erlang.crypt file.
- See
- beam_lib(3)
- for details.
+ For details, see
+ beam_lib(3) .
makedep
-
-
Produce a Makefile rule to track headers dependencies.
+
Produces a Makefile rule to track headers dependencies.
No object file is produced.
By default, this rule is written to
- .Pbeam]]> . However, if the option
+ .Pbeam]]> . However, if option
binary is set, nothing is written and the rule is
returned in Binary .
- For instance, if one has the following module:
+
For example, if you have the following module:
-module(module).
-include_lib("eunit/include/eunit.hrl").
--include("header.hrl").
-
- Here is the Makefile rule generated by this option:
+-include("header.hrl").
+ The Makefile rule generated by this option looks as follows:
module.beam: module.erl \
/usr/local/lib/erlang/lib/eunit/include/eunit.hrl \
- header.hrl
-
+ header.hrl
Write generated rule(s) to
Writes generated rules to Change the name of the rule emitted to Changes the name of the rule emitted to Consider missing headers as generated files and add them to the
+ Considers missing headers as generated files and adds them to the
dependencies.
Add a phony target for each dependency.
+ Adds a phony target for each dependency.
Produces a listing of the parsed code after preprocessing
+ Produces a listing of the parsed code, after preprocessing
and parse transforms, in the file
Produces a listing of the code after all source code
+ Produces a listing of the code, after all source code
transformations have been performed, in the file
This is a short form for both A short form for both If this flag is set, then
+ If this flag is set,
If this flag is set, then an extra field containing
- If this flag is set, an extra field, containing
+ This is a short form for both A short form for both Causes more verbose information from the compiler
+ Causes more verbose information from the compiler,
describing what it is doing. Add Adds the base name of the compiled file; The base name of the compiled file the directories specified using the The directories specified using option The input file is expected to be assembler code (default
- file suffix ".S"). Note that the format of assembler files
- is not documented, and may change between releases.
The input file is expected to be core code (default - file suffix ".core"). Note that the format of core files - is not documented, and may change between releases.
+ file suffix ".core"). Notice that the format of core files + is not documented, and can change between releases.This option is not recommended.
By default, the generated code for
- the
Makes the function
From R14A and forward, the compiler resolves calls +
As from R14A and forward, the compiler resolves calls
without module prefix to local or imported functions before
- trying auto-imported BIFs. If the BIF is to be
+ trying with auto-imported BIFs. If the BIF is to be
called, use the
If this option is written in the source code, as a
-compile({no_auto_import,[error/1]}).
Do not auto import any functions from the module
Do not auto-import any functions from
Omit line number information in order to produce a slightly +
Omits line number information to produce a slightly smaller output file.
If warnings are turned on (the
If warnings are turned on (option
In the descriptions that follow, the form that is used to change + the default value are listed.
Causes warnings to be emitted for malformed format
strings as arguments to
The default verbosity is
This option is removed, it will generate a fatal error if used.
+This option is removed, it generates a fatal error if used.
Beginning with R14A, the compiler no longer calls the +
As from beginning with R14A, the compiler no longer calls the
auto-imported BIF if the name clashes with a local or
- explicitly imported function and a call without explicit
- module name is issued. Instead the local or imported
- function is called. Still accepting
The use of this option has always been strongly discouraged. - From OTP R14A and forward it's an error to use it.
+The use of this option has always been discouraged. + As from R14A, it is an error to use it.
To resolve BIF clashes, use explicit module names or the
This option is removed, it will generate a fatal error if used.
+This option is removed, it generates a fatal error if used.
The use of this option has always been strongly discouraged. - From OTP R14A and forward it's an error to use it.
+The use of this option has always been discouraged. + As from R14A, it is an error to use it.
To resolve BIF clashes, use explicit module names or the
Causes a warning to be emitted if the
Emits a warning if option
Causes warnings to be emitted for all implicitly
- exported variables referred to after the primitives
- where they were first defined. No warnings for exported
- variables unless they are referred to in some pattern,
- which is the default, can be selected by the option
-
Emits warnings for all implicitly exported variables + referred to after the primitives where they were first defined. + By default, the compiler only emits warnings for exported + variables referred to in a pattern.
Causes warnings to be emitted for "fresh" variables
- in functional objects or list comprehensions with the same
- name as some already defined variable. The default is to
- warn for such variables. No warnings for shadowed
- variables can be selected by the option
-
Turns off warnings for "fresh" variables + in functional objects or list comprehensions with the same + name as some already defined variable. Default is to + emit warnings for such variables.
Turns off warnings for unused local functions.
- By default (
Turns off warnings for unused local functions. Default
+ is to emit warnings for all local functions that are not called
directly or indirectly by an exported function.
The compiler does not include unused local functions in
the generated beam file, but the warning is still useful
@@ -519,148 +517,142 @@ module.beam: module.erl \
Turns off warnings for unused local functions as
- Turns off warnings for unused local functions like
+ Turns off warnings for calls to deprecated functions. By
- default ( Turns off warnings for calls to deprecated functions. Default
+ is to emit warnings for every call to a function known by the
+ compiler to be deprecated. Notice that the compiler does not know
+ about attribute
Turns off warnings for calls to deprecated functions as
-
Turns off warnings for calls to deprecated functions like
+
Turns off warnings for uses of deprecated types. By
- default (
Turns off warnings for use of deprecated types. Default + is to emit warnings for every use of a type known by the compiler + to be deprecated.
Causes warnings to be emitted for calls to old type
- testing BIFs such as
Emits warnings for calls to old type testing BIFs,
+ such as
Causes warnings to be emitted for unused imported
- functions. No warnings for unused imported functions,
- which is the default, can be selected by the option
-
Emits warnings for unused imported functions. + Default is to emit no warnings for unused imported functions.
By default, warnings are emitted for variables which - are not used, with the exception of variables beginning - with an underscore ("Prolog style warnings"). +
By default, warnings are emitted for unused variables, + except for variables beginning with an underscore + ("Prolog style warnings"). Use this option to turn off this kind of warnings.
Turns off warnings for unused record types. By
- default (
Turns off warnings for unused record types. Default is to + emit warnings for unused locally defined record types.
Another class of warnings is generated by the compiler
during optimization and code generation. They warn about
patterns that will never match (such as
Note that the compiler does not warn for expressions that it
- does not attempt to optimize. For instance, the compiler tries
- to evaluate
Currently, those warnings cannot be disabled (except by +
Those warnings cannot be disabled (except by disabling all warnings).
+The compiler does not warn for expressions that it
+ does not attempt to optimize. For example, the compiler tries
+ to evaluate
Obviously, the absence of warnings does not mean that +
The absence of warnings does not mean that there are no remaining errors in the code.
Note that all the options except the include path
- ( All options, except the include path
+ ( Note also that the The options
For debugging of the compiler, or for pure curiosity,
the intermediate code generated by each compiler pass can be
inspected.
- A complete list of the options to produce list files can be
- printed by typing
Unrecognized options are ignored.
+Unrecognized options are ignored.
Both
-[{FileName,[ErrorInfo]}].
-
-
- Is the same as
Analogous to
Uses an
Determines whether the compiler would generate a
Determines whether the compiler generates a
Works exactly like
Works like
Works exactly like
Works like
Works exactly like +
Works like
The (host operating system) environment variable
The list will be appended to any options given to +
The list is appended to any options given to
When a function is inlined, the original function will be +
When a function is inlined, the original function is
kept if it is exported (either by an explicit export or if the
-
Inlining does not necessarily improve running time. - For instance, inlining may increase Beam stack usage which will - probably be detrimental to performance for recursive functions. + For example, inlining can increase Beam stack use, which + probably is detrimental to performance for recursive functions.
-Inlining is never default; it must be explicitly enabled with a +
Inlining is never default. It must be explicitly enabled with a
compiler option or a
To enable inlining, either use the
To enable inlining, either use the option
Example of explicit inlining:
@@ -817,33 +811,30 @@ pi() -> 3.1416.Example of implicit inlining:
--compile(inline). -+-compile(inline). -
The
The option
Example:
%% Aggressive inlining - will increase code size.
-compile(inline).
--compile({inline_size,100}).
-
+-compile({inline_size,100}).
The compiler can also inline a variety of list manipulation functions - from the stdlib's lists module.
+The compiler can also inline various list manipulation functions
+ from the module
This feature must be explicitly enabled with a compiler option or a
To enable inlining of list functions, use the
To enable inlining of list functions, use option
The following functions are inlined:
The
The
-{ErrorLine, Module, ErrorDescriptor}
-
+{ErrorLine, Module, ErrorDescriptor}
- A string describing the error is obtained with the following call:
-Module:format_error(ErrorDescriptor)
-
+Module:format_error(ErrorDescriptor)
The Compiler application compiles Erlang +
The
This document describes the changes made to the Compiler application.
++ The compiler optimizes away building of terms that are + never actually used. As a result, the compiler in OTP 18 + may produce more warnings for terms that are built but + not used than the compiler in OTP 17.
++ Own Id: OTP-12453
++ Using a map could incorrectly suppress warnings for + unused variables.
++ Own Id: OTP-12515
+
+ The compiler now properly reports unknown parse
+ transforms. That is,
+ Own Id: OTP-12723
++ Allow for 'creation of sub binary delayed' optimization + if maps instructions are in a clause.
++ Own Id: OTP-12758
+
+ The
+ Own Id: OTP-11978
+
+ The deprecated '
+ *** POTENTIAL INCOMPATIBILITY ***
++ Own Id: OTP-12100
++ Support variables as Map keys in expressions and patterns
+Erlang will accept any expression as keys in Map + expressions and it will accept literals or bound + variables as keys in Map patterns.
++ Own Id: OTP-12218
++ Infer Map type information in beam_type compiler + optimization pass.
++ Own Id: OTP-12253
++ Compiler optimizations have been improved.
++ Own Id: OTP-12393
+
+ Five undocumented functions in the module
+ Own Id: OTP-12497
++ Change some internal data structures to Maps in order to + speed up compilation time. Measured speed up is around + 10%-15%.
++ Own Id: OTP-12774
++ Fix beam_bool pass for Maps instruction get_map_elements
++ Before beam_split the get_map_elements instruction is + still in blocks and the helper function in beam_jump did + not reflect this.
++ Own Id: OTP-12844 Aux Id: 17
+This document describes the changes made to the Compiler application.
+
+ Fix
+ Instruction
+ Own Id: OTP-12967
+EEP43: New data type - Maps
- With Maps you may for instance:
For information on how to use Maps please see Map Expressions in the
The current implementation is without the following
- features:
Note that Maps is experimental during OTP 17.0.
--
cgit v1.2.3
From f4a0ae1736216feac5ae053610644bba2e12ed34 Mon Sep 17 00:00:00 2001
From: Erlang/OTP This document describes the changes made to the Compiler
application.
+ Fix cerl_trees:label/2 bug with map K/V swap
+ Own Id: OTP-13091
+ Warnings produced when the '
+ Own Id: OTP-13113 This document describes the changes made to the Compiler
application.
+ An complicated guard expression in a function call could
+ crash the compiler. (Thanks to Thomas Arts for reporting
+ this bug.)
+ Own Id: OTP-13208 Constructing a map in a guard in a catch could crash
+ the compiler. (Thanks to Thomas Arts for reporting this
+ bug.)
+ Own Id: OTP-13223 Updating a fun as if it were a map would cause the
+ compiler to crash. (Thanks to Thomas Arts for reporting
+ this bug.)
+ Own Id: OTP-13231
+ Fix pretty printing of Core Maps
+ Literal maps could cause Dialyzer to crash when pretty
+ printing the results.
+ Own Id: OTP-13238
+ A complex combination of bit syntax matching operations
+ would cause an internal consistency check failure during
+ compilation. (Thanks to Jose Valim for reporting this
+ bug.)
+ Own Id: OTP-13309 This document describes the changes made to the Compiler
application.
+ Own Id: OTP-13430 Aux Id: ERL-113
+ Optimization of tuple matching has been slightly
+ improved.
+ Own Id: OTP-12951 Five deprecated and undocumented functions in the
+ module
+ Own Id: OTP-12979 The pre-processor can now expand the ?FUNCTION_NAME
+ and ?FUNCTION_ARITY macros.
+ Own Id: OTP-13059 The function mapfold/4 has been added to the
+
+ Own Id: OTP-13280 Bitstring comprehensions have been generalized to
+ allow arbitrary expressions in the construction part.
+ Own Id: OTP-13289 The compiler will now produce warnings for binary
+ patterns that will never match (example:
+
+ Own Id: OTP-13374 Aux Id: ERL-44 The compiler will no longer put the compilation date
+ and time into BEAM files. That means that two BEAM files
+ compiled on the same computer from the same source code
+ and compilation options will be identical. Note: If you want to find out whether a BEAM file on
+ disk is different from the loaded code, compared the MD5
+ value obtained from
+ *** POTENTIAL INCOMPATIBILITY ***
+ Own Id: OTP-13504 This document describes the changes made to the Compiler
application.
- Own Id: OTP-13430 Aux Id: ERL-113
- Optimization of tuple matching has been slightly
- improved.
- Own Id: OTP-12951 Five deprecated and undocumented functions in the
- module
- Own Id: OTP-12979 The pre-processor can now expand the ?FUNCTION_NAME
- and ?FUNCTION_ARITY macros.
- Own Id: OTP-13059 The function mapfold/4 has been added to the
-
- Own Id: OTP-13280 Bitstring comprehensions have been generalized to
- allow arbitrary expressions in the construction part.
- Own Id: OTP-13289 The compiler will now produce warnings for binary
- patterns that will never match (example:
-
- Own Id: OTP-13374 Aux Id: ERL-44 The compiler will no longer put the compilation date
- and time into BEAM files. That means that two BEAM files
- compiled on the same computer from the same source code
- and compilation options will be identical. Note: If you want to find out whether a BEAM file on
- disk is different from the loaded code, compared the MD5
- value obtained from
- *** POTENTIAL INCOMPATIBILITY ***
- Own Id: OTP-13504 This document describes the changes made to the Compiler
application.
+ Own Id: OTP-13430 Aux Id: ERL-113 Dialyzer no longer crashes when there is an invalid
+ function call such as
+ Own Id: OTP-13552
+ Optimization of tuple matching has been slightly
+ improved.
+ Own Id: OTP-12951 Five deprecated and undocumented functions in the
+ module
+ Own Id: OTP-12979 The pre-processor can now expand the ?FUNCTION_NAME
+ and ?FUNCTION_ARITY macros.
+ Own Id: OTP-13059 The function mapfold/4 has been added to the
+
+ Own Id: OTP-13280 Bitstring comprehensions have been generalized to
+ allow arbitrary expressions in the construction part.
+ Own Id: OTP-13289 The compiler will now produce warnings for binary
+ patterns that will never match (example:
+
+ Own Id: OTP-13374 Aux Id: ERL-44 The compiler will no longer put the compilation date
+ and time into BEAM files. That means that two BEAM files
+ compiled on the same computer from the same source code
+ and compilation options will be identical. Note: If you want to find out whether a BEAM file on
+ disk is different from the loaded code, compared the MD5
+ value obtained from
+ *** POTENTIAL INCOMPATIBILITY ***
+ Own Id: OTP-13504 This document describes the changes made to the Compiler
application.
- Own Id: OTP-13430 Aux Id: ERL-113 Dialyzer no longer crashes when there is an invalid
- function call such as
- Own Id: OTP-13552
- Optimization of tuple matching has been slightly
- improved.
- Own Id: OTP-12951 Five deprecated and undocumented functions in the
- module
- Own Id: OTP-12979 The pre-processor can now expand the ?FUNCTION_NAME
- and ?FUNCTION_ARITY macros.
- Own Id: OTP-13059 The function mapfold/4 has been added to the
-
- Own Id: OTP-13280 Bitstring comprehensions have been generalized to
- allow arbitrary expressions in the construction part.
- Own Id: OTP-13289 The compiler will now produce warnings for binary
- patterns that will never match (example:
-
- Own Id: OTP-13374 Aux Id: ERL-44 The compiler will no longer put the compilation date
- and time into BEAM files. That means that two BEAM files
- compiled on the same computer from the same source code
- and compilation options will be identical. Note: If you want to find out whether a BEAM file on
- disk is different from the loaded code, compared the MD5
- value obtained from
- *** POTENTIAL INCOMPATIBILITY ***
- Own Id: OTP-13504 Return compiler options given via the environment variable
+
+
+
+
+
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
The list can be retrieved with
+
The list can be retrieved with
-
This document describes the changes made to the Compiler application.
++ Own Id: OTP-13430 Aux Id: ERL-113
+Dialyzer no longer crashes when there is an invalid
+ function call such as
+ Own Id: OTP-13552 Aux Id: ERL-138
++ Optimization of tuple matching has been slightly + improved.
++ Own Id: OTP-12951
+Five deprecated and undocumented functions in the
+ module
+ Own Id: OTP-12979
+The pre-processor can now expand the ?FUNCTION_NAME + and ?FUNCTION_ARITY macros.
++ Own Id: OTP-13059
+The function mapfold/4 has been added to the
+
+ Own Id: OTP-13280
+Bitstring comprehensions have been generalized to + allow arbitrary expressions in the construction part.
++ Own Id: OTP-13289
+The compiler will now produce warnings for binary
+ patterns that will never match (example:
+
+ Own Id: OTP-13374 Aux Id: ERL-44
+The compiler will no longer put the compilation date + and time into BEAM files. That means that two BEAM files + compiled on the same computer from the same source code + and compilation options will be identical.
+Note: If you want to find out whether a BEAM file on
+ disk is different from the loaded code, compared the MD5
+ value obtained from
+ *** POTENTIAL INCOMPATIBILITY ***
++ Own Id: OTP-13504
+The function
+ Own Id: OTP-13654
+