This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Format checking update
- To: <gcc-patches at gcc dot gnu dot org>
- Subject: Format checking update
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Mon, 29 Jan 2001 23:44:53 +0000 (GMT)
I've installed the following patch to update the format checking projects
list in htdocs/projects/index.html.
Can I have maintainership of the format checking code (c-format.c,
gcc.dg/format, code elsewhere calling format checking code / handling
format checking command line options) itself, as the only person to have
done any much work on it lately?
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/index.html,v
retrieving revision 1.10
diff -u -r1.10 index.html
--- index.html 2001/01/15 07:42:23 1.10
+++ index.html 2001/01/29 23:27:17
@@ -258,7 +258,11 @@
<li><code>strftime</code>: warnings for use of <code>0</code>,
<code>-</code> or <code>_</code> flags without width on formats where
-inappropriate.</li>
+inappropriate. Similar warnings where use of one format feature is
+useless unless another one is also used also apply for
+<code>printf</code> formats (<code>0</code> and <code>-</code> flags
+when no width is specified and so there is no padding) and for
+<code>strfmon</code> formats.</li>
<li>Integer <code>printf</code> formats: warn for integer constant
argument out of range of unpromoted type (including signed/unsigned
@@ -268,18 +272,6 @@
list of format argument have the correct boundedness
qualification.</li>
-<li>Make <code>-Wformat=2</code> work for C++ (rather than being
-silently ignored).</li>
-
-<li>Warn for format checking options that have no effect when used
-without <code>-Wformat</code> (for example, if
-<code>-Wformat-nonliteral</code> is used on its own); <a
-href="http://gcc.gnu.org/ml/gcc-patches/2000-12/msg00383.html">patch
-available</a>.</li>
-
-<li>Add checking for <code>strfmon</code> formats (a feature of the
-Single Unix Specification, but not part of ISO C).</li>
-
<li>Fix detection of whether format strings are narrow or wide on
targets where <code>wchar_t</code> is <code>char</code>. This may
require changes elsewhere in the compiler to mark string constants
@@ -303,6 +295,20 @@
href="http://gcc.gnu.org/ml/gcc/2000-12/msg00170.html">message
soliciting views on the user interface to this</a> and send any views
on this to the <code>gcc</code> mailing list.</li>
+
+<li>Clean up how <code>format.exp</code> handles
+<code>TORTURE_OPTIONS</code>, by making changes elsewhere in the test
+harness so that <code>TORTURE_OPTIONS</code> is initialized for each
+<code>dg-init</code> rather than just once and so needing saving and
+restoring.</li>
+
+<li>When a <code>format</code> or <code>format_arg</code> attribute is
+applied to a function with a non-prototype declaration, and the
+function is later redeclared with a prototype or defined, the
+attribute should be checked again to see if it makes sense given the
+argument types of the function. Similarly, these checks should be
+made if the original attribute is on an old-style function
+definition.</li>
<li>Handle format attributes on function pointers and typedefs; see <a
href="http://gcc.gnu.org/ml/gcc/2000-09/msg00339.html">a message about
--
Joseph S. Myers
jsm28@cam.ac.uk