From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9859 invoked by alias); 31 Jul 2004 22:30:11 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 9851 invoked by alias); 31 Jul 2004 22:30:11 -0000 Date: Sat, 31 Jul 2004 22:30:00 -0000 Message-ID: <20040731223011.9850.qmail@sourceware.org> From: "jsm at polyomino dot org dot uk" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040730123357.16833.timb@bluearc.com> References: <20040730123357.16833.timb@bluearc.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c/16833] -fno-builtin prevents automatic format checks for standard functions X-Bugzilla-Reason: CC X-SW-Source: 2004-07/txt/msg03711.txt.bz2 List-Id: ------- Additional Comments From jsm at polyomino dot org dot uk 2004-07-31 22:30 ------- Subject: Re: New: -fno-builtin prevents automatic format checks for standard functions On Fri, 30 Jul 2004, timb at bluearc dot com wrote: > The documentation for the format function attribute says: "The compiler always > (unless -ffreestanding is used) checks formats for the standard library > functions ... whenever such warnings are requested". However, these implicit > attributes appear to be disabled also by -fno-builtin (which is implied by > -ffreestanding). This would be a result of the changes to unify all the built-in attribute handling under the auspices of built-in functions (rather than having some handled one way and some handled the other way). Thus, it is an intended change and a documentation bug; -fno-builtin now disables all the special handling of particular function names (except for that using the remaining routes to such special handling, special_function_p and cp/cfns.gperf). You can of course use attributes in the headers declaring the standard format functions to get these warnings even with -fno-builtin. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16833