This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Possible errors in call to output_operand_lossage?
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: Richard Henderson <rth at redhat dot com>
- Cc: Philipp Thomas <pthomas at suse dot de>, <gcc-bugs at gcc dot gnu dot org>, Philipp Thomas <philippt at t-online dot de>
- Date: Sat, 2 Feb 2002 01:50:39 +0000 (GMT)
- Subject: Re: Possible errors in call to output_operand_lossage?
On Fri, 1 Feb 2002, Richard Henderson wrote:
> On Sat, Feb 02, 2002 at 12:03:49AM +0100, Philipp Thomas wrote:
> > The following calls to output_operand_lossage seem be wrong as they
> > use '%' instead of '%%' and thus xgettext will mark them as C format and
> > then msgfmt will fail because things like %A are no valid format specifiers.
>
> They are not printf format. Existing uses are correct.
Shouldn't we fix gettext so particular functions can be marked as
non-C-format functions, so it doesn't then mark any of the msgid arguments
to those functions as c-format, rather than marking every call?
Anyway, %A is a valid printf format, albeit not being used as a printf
format here. If it can't handle valid C99 formats, what does it think of
the printf extensions used in GCC's diagnostics?
--
Joseph S. Myers
jsm28@cam.ac.uk