-zastd= infinite loop with unknown value

[fuhsnn]

Passing options like -zastd=c11 -zastd=c++03 to wcc/wpp causes them to freeze with 100% cpu use.

This is the kind of option that people will try their luck with, and build systems might attempt to probe it; should be worthwhile to make it more well behaved.

It looks like the option parser only increment for known values, so for c11 the global char pointer will likely be stuck at '1'.

open-watcom-v2/bld/cc/c/coptions.c

Lines 189 to 197 in a3d9dea

	while( !CmdScanSwEnd() ) {
	if( CmdRecogChar( 'c' ) ) {
	if( CmdRecogChar( '8' ) && CmdRecogChar( '9' ) ) {
	cstd = STD_C89;
	} else if( CmdRecogChar( '9' ) && CmdRecogChar( '9' ) ) {
	cstd = STD_C99;
	}
	}
	}

open-watcom-v2/bld/plusplus/c/cmdlnany.c

Lines 124 to 138 in a3d9dea

	while( !CmdScanSwEnd() ) {
	if( CmdRecogChar( 'c' )
	&& CmdRecogChar( '+' )
	&& CmdRecogChar( '+' ) ) {
	if( CmdRecogChar( '9' )
	&& CmdRecogChar( '8' ) ) {
	cxxstd = STD_CXX98;
	fail = false;
	} else if( CmdRecogChar( '0' )
	&& CmdRecogChar( 'x' ) ) {
	cxxstd = STD_CXX0X;
	fail = false;
	}
	}
	}

[jmalak]

Thanks for your bug repport.
I think there should be a message about unsupported value and setup to latest supported value and skip unsupported value.

[negge]

I just ran into this infinite loop issue by passing -zastd=C99

[jmalak]

It is fixed now and C compiler reports incorrect value and correctly process rest of option value.