sys_core_fold: Strengthen optimization of letrecs in effect context

We used to evaluate the body of a 'letrec' in value context, even
if the 'letrec' was being evaluated in effect context. In most
cases, the context does not matter because the body is usually
just an 'apply' which will never be optimized away.

However, in the case of incorrect code described in the previous
commit, it does matter. We can find such bad code by evaluating
the body in effect context. For example, if we have the following
incorrect code:

  letrec
    f/1 = fun(A) -> ... <use of Var> ...
    in let Var = <<2:301>>
       in apply(Arg)

If the letrec is evaluated in effect context, the code will be
reduced to:

  letrec
    f/1 = fun(A) -> ... <use of Var> ...
    in seq Var = <<2:301>> do apply(Arg)

Now Var will be unbound and a later compiler pass will crash to
ensure that the bad Core Erlang code is noticed.

Also add a test case to ensure that the compiler crashes if the
bug fixed in the previous commit re-surfaces.

1 files changed, 1 insertions, 1 deletions

diff --git a/lib/compiler/src/sys_core_fold.erl b/lib/compiler/src/sys_core_fold.erl
index 09716d0866..e079fc072a 100644
--- a/lib/compiler/src/sys_core_fold.erl
+++ b/lib/compiler/src/sys_core_fold.erl
@@ -313,7 +313,7 @@ expr(#c_letrec{defs=Fs0,body=B0}=Letrec, Ctxt, Sub) ->
     Fs1 = map(fun ({Name,Fb}) ->
 		      {Name,expr(Fb, {letrec,Ctxt}, Sub)}
 	      end, Fs0),
-    B1 = body(B0, value, Sub),
+    B1 = body(B0, Ctxt, Sub),
     Letrec#c_letrec{defs=Fs1,body=B1};
 expr(#c_case{}=Case0, Ctxt, Sub) ->
     %% Ideally, the compiler should only emit warnings when there is