gensupport: validate compact constraint modifiers

For constraints there are operand modifiers and constraint qualifiers.
Operand modifiers apply to all alternatives and must appear, in
traditional syntax before the first alternative.  Constraint
qualifiers, on the other hand must appear in each alternative to which
they apply.

There's no easy way to validate the distinction in the traditional md
format, but when using the new compact format we can enforce some
semantic checking of these characters to avoid some potentially
surprising code generation.

gcc/

	* gensupport.cc (conlist::conlist): Pass a location to the constructor.
	Only allow skipping of non-alpha-numeric characters when parsing a
	number and only allow '=', '+' or '%'.  Add some error checking when
	parsing an operand number.
	(parse_section_layout): Pass the location to the conlist constructor.
	(parse_section): Allow an optional list of forbidden characters.
	If specified, reject strings containing them.
	(convert_syntax): Reject '=', '+' or '%' in an alternative.

0 files changed, 0 insertions, 0 deletions