On Sat, Jan 09, 2021 at 07:44:31PM +0100, Matthias Klose wrote:
> These warnings, including the suggested fixes are seen on power*-linux builds.
>
> warning: misspelled term 'builtin function' in format; use 'bult-in function'
Are you sure it printed bult-in ?
> fatal_error (input_location,
> - "internal error: builtin function %qs already processed",
> + "internal error: builtin-function %qs already processed",
It meant built-in function instead of builtin-function I'm pretty sure.
> name);
>
> rs6000_builtin_decls[(int)code] = t =
> @@ -11219,7 +11219,7 @@ altivec_expand_builtin (tree exp, rtx target, bool
> *expandedp)
> {
> size_t uns_fcode = (size_t) fcode;
> const char *name = rs6000_builtin_info[uns_fcode].name;
> - error ("Second argument of %qs must be in the range [0, 3].", name);
> + error ("Second argument of %qs must be in the range [0, 3]", name);
Diagnostics shouldn't start with capital letter either, so it should be
"second ..."
> - "internal error: builtin function %qs had an unexpected "
> + "internal error: builtin-function %qs had an unexpected "
> "return type %qs", name, GET_MODE_NAME (h.mode[0]));
> - "internal error: builtin function %qs, argument %d "
> + "internal error: builtin-function %qs, argument %d "
See above.
Jakub
