+=item *
+
+Compilation of anonymous constants (e.g., C<sub () { 3 }>) no longer
+deletes any subroutine named C<__ANON__> in the current package. Not only
+was C<*__ANON__{CODE}> cleared, but there was a memory leak, too. This bug
+goes back to perl 5.8.0.
+
+=item *
+
+Stub declarations like C<sub f;> and C<sub f ();> no longer wipe out
+constants of the same name declared by C<use constant>. This bug was
+introduced in perl 5.10.0.
+
+=item *
+
+Under some conditions a warning raised in compilation of regular
+expression patterns could be displayed multiple times. This is now
+fixed.
+
+=item *
+
+C<qr/[\N{named sequence}]/> now works properly in many instances. Some
+names known to C<\N{...}> refer to a sequence of multiple characters,
+instead of the usual single character. Bracketed character classes
+generally only match single characters, but now special handling has
+been added so that they can match named sequences, but not if the class
+is inverted or the sequence is specified as the beginning or end of a
+range. In these cases, the only behavior change from before is a slight
+rewording of the fatal error message given when this class is part of a
+C<?[...])> construct. When the C<[...]> stands alone, the same
+non-fatal warning as before is raised, and only the first character in
+the sequence is used, again just as before.
+
+=item *
+
+Tainted constants evaluated at compile time no longer cause unrelated
+statements to become tainted. [perl #122669]
+
+=item *
+
+C<open $$fh, ...>, which vivifies a handle with a name like "main::_GEN_0",
+was not giving the handle the right reference count, so a double free could
+happen.
+
+=item *
+
+When deciding that a bareword was a method name, the parser would get
+confused if an "our" sub with the same name existed, and look up the method
+in the package of the "our" sub, instead of the package of the invocant.
+
+=item *
+
+The parser no longer gets confused by C<\U=> within a double-quoted string.
+It used to roduce a syntax error, but now compiles it correctly.
+[perl #80368]
+
+=item *
+
+It has always been the intention for the C<-B> and C<-T> file test
+operators to treat UTF-8 encoded files as text.
+(L<perlfunc|perlfunc/-X FILEHANDLE> has been updated to say this.)
+Previously, it was possible for some files to be considered UTF-8 that
+actually weren't valid UTF-8. This is now fixed. The operators now
+work on EBCDIC platforms as well.
+
+=item *
+
+Under some conditions warning messages raised during regular expression
+pattern compilation were being output more than once. This has now been
+fixed.
+
+=item *
+
+A regression has been fixed that was introduced in v5.20.0 (fixed in
+v5.20.1 as well as here) in which a UTF-8 encoded regular expression
+pattern that contains a single ASCII lowercase letter does not match its
+uppercase counterpart. [perl #122655]
+
+=item *
+
+Constant folding could incorrectly suppress warnings if lexical warnings
+(C<use warnings> or C<no warnings>) were not in effect and C<$^W> were
+false at compile time and true at run time.
+
+=item *
+
+Loading UTF8 tables during a regular expression match could cause assertion
+failures under debugging builds if the previous match used the very same
+regular expression. [perl #122747]
+
+=item *
+
+Thread cloning used to work incorrectly for lexical subs, possibly causing
+crashes or double frees on exit.
+
+=item *
+
+Since perl 5.14.0, deleting C<$SomePackage::{__ANON__}> and then undefining
+an anonymous subroutine could corrupt things internally, resulting in
+L<Devel::Peek> crashing or L<B.pm|B> giving nonsensical data. This has
+been fixed.
+
+=item *
+
+C<(caller $n)[3]> now reports names of lexical subs, instead of treating
+them as "(unknown)".
+
+=item *
+
+C<sort subname LIST> now supports lexical subs for the comparison routine.
+