It sounds strange what you are reporting.. in my little experience I noticed that when multiple errors are found during -c compilation, the first one is the meaningfull one and if are reported additional errors they many times caused by the first one. Then others errors can be found and reported, but I suspect this depend on which kind of errors is the first and if compiler can go on.

Probably you should reduce what you are experiencing into a minimal amount of code that produces such behaviours under these version and include, if still true, more information like perl -v gives.

I've tried in different perl distros ( 5.14 5.22 5.24 strawberry portable) and I got the same output under -c simply modifing a large file introducing 3 errors the first one at line 300 consisting into a if($condition){ continue{1} ...

"my" variable $par_fname masks earlier declaration in same scope at
        ERRORS.pl line 316 (#1)
    (W misc) A "my", "our" or "state" variable has been redeclared in 
+the
    current scope or statement, effectively eliminating all access to 
+the
    previous instance.  This is almost always a typographical error.  
+Note
    that the earlier variable will still exist until the end of the sc
+ope
    or until all closure references to it are destroyed.

syntax error at ERRORS.pl line 300, near "continue"
syntax error at eERRORS.pl line 310, near "}"
Can't use global $& in "my" at ERRORS.pl line 316, near "uc($&"
syntax error at ERRORS.pl line 401, near "log_stdout"
syntax error at ERRORS.pl line 641, near "}"
syntax error at ERRORS.pl line 734, near "}"
syntax error at ERRORS.pl line 743, near "}"
Can't redeclare "my" in "my" at ERRORS.pl line 745, near ""
syntax error at ERRORS.pl line 782, near "}"
Can't redeclare "my" in "my" at ERRORS.pl line 788, near ""
ERRORS.pl has too many errors (#2)
    (F) Probably means you had a syntax error.  Common reasons include
+:


...
[download]

L*