Perl or Compiler?

GE
Built 5.26.2 successfully, and then added -DDEBUGGING option.
All goes well except for recomp.c...

> Compiling : ..\reentr.c
> Compiling : ..\regcomp.c
> ..\regcomp.c(20770): Error! E1118: ***FATAL*** segment too large
> Makefile:1020: recipe for target 'workdbg/regcomp.obj' failed
> Compiling : ..\regexec.c
> Compiling : ..\run.c

Is this a Perl or Compiler problem?

Norm
0
normw
4/14/2018 1:01:01 AM
perl.perl5.porters 47254 articles. 0 followers. Follow

1 Replies
40 Views

Similar Articles

[PageSpeed] 35

GE,
RTM is well enough known, but it turned out I needed to read more than 
the error message, since it offered no clues. (even in the manual.) 
Eventually discovered the DEBUG flags and by reducing the amount of 
debug info, was able to get the entire source to compile without issue.
FWIW
The compiler shows the following warnings, but not being GCC not sure if 
that counts for much.
> ..\locale.c(952): Warning! W200: 'locale_param' has been referenced but never assigned a value
> ..\mg.c(369): Warning! W107: Missing return value for function 'Perl_mg_size'
> ..\op.c(1546): Warning! W107: Missing return value for function 'Perl_op_contextualize'
> ..\pp_pack.c(567): Warning! W107: Missing return value for function 'S_group_end'
> ..\vutil.c(335): Warning! W124: Comparison result always 0
> ..\vutil.c(585): Warning! W124: Comparison result always 0
> ..\util.c(4560): Warning! W124: Comparison result always 1
Thx
Norm

On 17/04/2018 7:49 AM, Dave Mitchell wrote:
> On Tue, Apr 17, 2018 at 07:49:10AM +1000, NormW wrote:
>> GM Dave,
>> Thanks for for the feedback. Will dig further at my end. By all the
>> references, GCC would be the one to use, but my fixation with NetWare
>> narrows the field.
>
> Note that some of the code in regcomp.c and regexec.c use macros which
> have very large expansions, especially on debugging builds. That may
> well trip up a compiler (either the macro is too long, or the function is
> too big).
>
0
normw
4/17/2018 1:01:01 AM
Reply: