Hi! In both cases starting with the UDR additions we are looking for any identifiers, both min and max are identifiers, so no need to mention them explicitly. They are just kind like predefined UDRs.
Committed to trunk. 2017-03-03 Jakub Jelinek <ja...@redhat.com> PR c/79837 * c-parser.c (c_parser_omp_clause_reduction): Don't mention %<min%> or %<max%> in the diagnostics, instead mention identifier. (c_parser_omp_declare_reduction): Don't mention %<min%> in the diagnostics. --- gcc/c/c-parser.c.jj 2017-03-03 20:53:36.000000000 +0100 +++ gcc/c/c-parser.c 2017-03-03 21:13:35.058836286 +0100 @@ -12112,7 +12112,7 @@ c_parser_omp_clause_reduction (c_parser default: c_parser_error (parser, "expected %<+%>, %<*%>, %<-%>, %<&%>, " - "%<^%>, %<|%>, %<&&%>, %<||%>, %<min%> or %<max%>"); + "%<^%>, %<|%>, %<&&%>, %<||%> or identifier"); c_parser_skip_until_found (parser, CPP_CLOSE_PAREN, 0); return list; } @@ -16960,7 +16960,7 @@ c_parser_omp_declare_reduction (c_parser default: c_parser_error (parser, "expected %<+%>, %<*%>, %<-%>, %<&%>, " - "%<^%>, %<|%>, %<&&%>, %<||%>, %<min%> or identifier"); + "%<^%>, %<|%>, %<&&%>, %<||%> or identifier"); goto fail; } Jakub