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?
* Richard Henderson (rth@redhat.com) [20020202 00:13]:
> > Sigh, that means we have yet another batch of files where messages have to
> > be marked for xgettext as not being printf format, right?
>
> Files? No. Just the one function call.
You can't (at least ATM) mark a function call as not taking printf style
strings, so you have to mark every call to o_o_l by inserting a comment.
This is the list of files that needed to be changed:
* final.c config/arc/arc.c config/a29k/a29k config/fr30/fr30.c
config/m32r/m32r.c config/ia64/ia64.c config/m88k/m88k.c
config/mips/mips.c config/romp/romp.c config/alpha/alpha.c
config/sparc/sparc.c config/rs6000/rs6000.c: Mark messages to
output_operand_lossage as not being printf style.
My question now is how to verify I didn't goof when inserting the necessary
comments. Would it suffice to configure a cross-compiler for the given cpu
and then just build the respective object file (i.e. arc.o, m88k.o etc. )?
Philipp
--
Philipp Thomas <pthomas@suse.de>
Development, SuSE Linux AG, Deutscherrnstr. 15-19, D-90429 Nuremberg, Germany